>But, for the record, use 0x4d415020ul for 'MAP '.
I've created the following macro for types:
#define BLOCK_TYPE( a,b,c,d ) ((unsigned long)(d | (c << 8) | (b
<< 16) | (a << 24)))
Which should solve the problem. I use this whenever defining a constant for
block type.
>Ok. You made me thing there was something there I was missing...
maybe that typo in "think" ? <g> ... couldn't resist
>Why not just use a dang enum or some defines?! What's with the structs?
there's only arrays, no structs. The advantage is that you can add a new
type w/o problems and my code just indexes the array.
>Or better, how about platform-specific read/write functions?
I don't think that's better. To get the first cross-platform OpenCard off
the ground we should try to keep platform-specific code as low as possible.
The less depends on platform-specific code, the less we need to port, the
faster we can release new versions. Also, platform specific code is another
place that can introduce differences between the same version of OpenCard.
If performance is too low we can slip in an OpenCard 1.5 which uses
platform-specific code to speed things up.
>Yes. The Mac headers define true and false when the compiler does not have
>support for them.
OK, then I'll switch to "true" and "false".
>MPW supports them (option "-bool on") and I'm betting CodeWarrior does,
>too. Egcs does.
CW has "true" and "false".
>I must not of compiled HelloWorld.cpp...don't know how...I'll have to try
>again.
May I return that rock to you? Might be a good place to hide under after
that mistake :-)
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
