Re: Replacement for MS STL?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"Garry W" <ListMail3@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:gbi0i2h5qksje13ijl5up3cu0737cl7f0e@xxxxxxxxxx

Ulrich Eckhardt <eckhardt@xxxxxxxxxxxxxx> wrote:
I think it's a lack of understanding on your side. The point is that I
must
be able to do this:

#define i 7*6
#define x 23,
#include <vector>

and still have a working vector afterwards. That is why that code, except
for the interfaces required by the standard, uses names reserved to the
compiler and standardlibrary implementation like __foo and _Bar.

Well, the MS STL -almost- always remembers to put the _'s in there. :)

Nope, it *always* does. The only names you'll find that aren't
"obfuscated" (defined in the implementer's name space) are the
ones mandated by the C++ Standard.

Here's the beginning of the MS STL "de-obfuscator" that I had, by
necessity,
started working on. Old internal names are on the left, replacement ones
are
on the right.
.....

So far, you've reported:

1) that you don't like the documented way that debugging gets
turned on and off, so you experimented at length and got in
some trouble

2) that you tried to do something with strings that's documented
as not supported, and you got in some trouble

3) that you *think* the names internal to the library are
inconsistent, and you *feel* they are in bad style

But you began this thread by saying:

: And I've given up on the Microsoft implementation. When I tried to use it
I
: immediately fell over several bugs in it that took a lot of time to find.
And
: working with it has been really difficult because the code is kind of
: illegible. At least for the uninitiated. (Apologies if there are authors
: here!)

So far you are zero for three, and seem to have trouble
reading documentation. But if you have other bugs to report,
I'm still very interested in hearing about them.

P.J. Plauger
Dinkumware, Ltd.
http://www.dinkumware.com


.

Relevant Pages

  • Re: Reviving REMARKS
    ... > fixed paragraph names encouraged the inclusion of significant ... The standard mavens, in their eternal and rather foolish quest ... "documentation prologs" out of programs and if not move them to ... Far more useful is a good source code management tool. ...
    (comp.lang.cobol)
  • Re: The Problems of TeX
    ... many TeX distributions did not come with it - OzTeX is one (in ... If your definition of "not exotic" is "everything that was standard x ... The MacTeX distribution is flawed in that it fails to provide the simple ... silly because it's purely down to a lack of decent documentation. ...
    (comp.text.tex)
  • VHDL Library Madness
    ... the documentation, but it's a tough thing to get changed. ... Appnote code is the hardest to fix. ... some coding standard. ... , go through all the example code which has "bad" libraries, ...
    (comp.lang.vhdl)
  • Re: CRT and Win32 SDK
    ... However, it might give a reader an impression that when doing embedded programming one typically has a full-fledged language at hand, where in effect the runtime library implements what the OS would provide on e.g. a PC. ... The C and C++ standards differentiate between hosted and free-standing implementation to deal with the special constraints of embedded programming, where free-standing doesn't need to provide all of the language's standard library, but even that distinction does in practice not go far enough: it might be that fundamental language features such as static variables and exceptions are not available on the embedded platform's language implementation. ... Both the user-mode Win32 API and the kernel ... The documentation remarks are very important parts of that documentation and form the main part of it. ...
    (microsoft.public.vc.language)
  • Re: Irish arms crisis again
    ... Tell Ghassan it's just entailing as opposed to a standard. ... Frank offset far? ... it'll bimonthly steal the documentation. ... Waleed's junction worth returns, it will shrilly supply the candle. ...
    (sci.crypt)