Typeof is next for review -- review manager needed

Hi everybody, I was recently contacted by Tom Brinkman (the review wizard) and told that, since the authors of other libraries in the queue are not yet ready to start, the Typeof libraty is being moved to be the next one for the review. Peder and I will be ready starting next Monday. We are making some final touches, and I will upload the review version very soon. The most recent version is now available in the Boost sandbox file vault, http://boost-sandbox.sourceforge.net/vault/, typeof.zip. In this regard, I would like to ask if somebody would like to give us an honor of being our review manager. Here is the short description of the library: ---- The proposed Typeof library implements the functionality of the non-standard typeof() operator. Depending on the compiler, it utilizes one of the following three methods: 1) Forwards to the non-standard typeof extension, usually called __typeof__, on the compilers where such extension is available; 2) Utilises a loophole, available on Microsoft vc6.5, vc7.0, and vc7.1; 3) Emulates typeof by the means of template and preprocessor metaprogramming for the compilers that do not fall into above two categories, such as vc8.0 beta, etc. The emulation works by bringing the expression into the context where its type is known, using partial template specializations to encode a type as a compile-time sequence of integer numbers, moving integers one-by-one into the original context through the sizeof(), and then reconstructing and decoding the sequence into the original type. This method requires the user to register types and templates, and compiles slower than the other two, but has a benefit of being standard-compliant and rather portable. It can also be used on the compilers that implement the __typeof__ as a language extension, when compiling with language extensions switched off. ---- Regards, Arkadiy

Arkadiy Vertleyb wrote:
Hi everybody,
I was recently contacted by Tom Brinkman (the review wizard) and told that, since the authors of other libraries in the queue are not yet ready to start, the Typeof libraty is being moved to be the next one for the review.
I wonder why typeof was pushed ahead of FOREACH. It's ready. As you can see from the Google cache of the review schedule page, FOREACH *was* scheduled ahead of typeof. http://tinyurl.com/3mk8a Is there an explanation? -- Eric Niebler Boost Consulting www.boost-consulting.com

I was recently contacted by Tom Brinkman (the review wizard) and told
"Eric Niebler" <eric@boost-consulting.com> wrote that,
since the authors of other libraries in the queue are not yet ready to start, the Typeof libraty is being moved to be the next one for the review.
I wonder why typeof was pushed ahead of FOREACH. It's ready. As you can see from the Google cache of the review schedule page, FOREACH *was* scheduled ahead of typeof.
Is there an explanation?
I guess this is a question to Tom... I am well aware that FOREACH is sheduled before TYPEOF, and of course, if it's ready, it should go first. Regards, Arkadiy

Arkadiy Vertleyb wrote:
"Eric Niebler" <eric@boost-consulting.com> wrote
Arkadiy Vertleyb wrote:
I was recently contacted by Tom Brinkman (the review wizard) and told that, since the authors of other libraries in the queue are not yet ready to start, the Typeof libraty is being moved to be the next one for the review.
I wonder why typeof was pushed ahead of FOREACH. It's ready. As you can see from the Google cache of the review schedule page, FOREACH *was* scheduled ahead of typeof.
Is there an explanation?
I guess this is a question to Tom...
I am well aware that FOREACH is sheduled before TYPEOF, and of course, if it's ready, it should go first.
I am still waiting for an answer to this question. Tom, why was TYPEOF moved ahead of FOREACH in the review queue? And why was it done without any discussion on the list? -- Eric Niebler Boost Consulting www.boost-consulting.com
participants (2)
-
Arkadiy Vertleyb
-
Eric Niebler