Re: stack before

[Justin F. <vh...@us...>]

> JF> with optional thread safety, so it's "fast enough", too.
> 
> sure. but once you asked me to write a simple stack for faestarter.
> which is now needed due to Lua.

That was when?  Long before I decided to create libfaeutil.  I thought 
we were sleeping for enough time already.

> JF> structures larger than "four byte integers".
> 
> and it ties you to C++ only.

Who cares?  Stack isn't what you want to use in other languages.  Other 
languages are typically interpreted and don't achieve speeds at which 
you benefit from the low-level-optimized code.

> or you gotta make interfaces. indeed, I
> had this idea too, it's very usefull, yes. but I wanted faestack to be
> as close to the real stack as possible.

It should function as close to the real stack, yes.  So does list<>.

> JF> issue has the lowest priority so far.
> 
> we'd even write our own garbage collector, as well.

Is this a false positive on my sarcasm detector?..  Garbage collectors 
have nothing to do with the concept of allocators in STL whatsoever.

> JF> That depends.  Never seen a "CONSTANT__", so I quite got used to the
> JF> "__CONSTANT" style.
> 
> yeah, like most people do. though, ANSI C forbids this, due to all
> identifiers start with "__" are reserved for compiler use. I'm not
> sure, but I think C++ standard does too, at least in global namespace.

How interesting!  I must find a copy of the standards.  Got some?

> P.S. I can't say something about Lua, yet. I've to read about it
> more..

Have fun!  Must be an interesting read.