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.
JF> structures larger than "four byte integers".
and it ties you to C++ only. 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.
JF> issue has the lowest priority so far.
we'd even write our own garbage collector, as well. avoid _stack_ as
is, and all these stray memory allocations.
JF> binary whats?
2 ^ x, thus it's fast than ever ;)
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.
P.S. I can't say something about Lua, yet. I've to read about it
more..
|
