21 Dec
2006
21 Dec
'06
7:08 p.m.
Chuck Guzis wrote:
That's the approach that I'd take--except
I'd have the first one
write a temp file with all of the initialzed goodies and have the
second one read it in. It's dirty, quick and modular--and maybe
easier to debug.
Ah, now there is an idea. Quite a bit easier to implement than my idea
of trying to leave it resident in memory. Startup will be glacial ..
Of course maybe this isn't worth the effort ...
I do know that not all C/C++ libraries are the same,
nor are C/C++
compilers. Some generate lots of calls to the library, which can
bring in all sorts of unneeded garbage. I've written C programs with
their own startup code that run fine without any C library at all.
I don't know if that's even possible in C++, however.
No need to fear C++. It's just C with some extras.
If you choose to dink with stuff like templates, polymorphism, etc. you
get what you deserve. Otherwise, I look at it like just a better C. I
use new and malloc as it suits me, and never use iostreams .. good old
stdio works just fine.
This compiler (Borland Turbo C++ 3.0) generates a map file so that I can
see what I dragged in, and correct my code accordingly.
Mike