At 6:14 PM +0200 on 5/25/99, M. Uli Kusterer wrote:
>* Anthony, do you agree on using the "JokerUtilities.h" file I sent you as
>the base header for the code? It's the one that contains the declaration of
>the class string for MPW, the assert and exception definition macros, the
>DEBUG flag and it includes the headers stdlib.h, ctype.h, string.h,
>stdexcept.h, iostream.h. Of course we'd rename "JokerUtilities.h" to
>"OCrdUtilities.h" or something else.
I think we should split our exception hierarchy off -- call it something like
"OpenCardExceptions.h" or "OCException.h"
>
>* Do we want to name deletion functions "Delete" or "Kill"?
Hmmm... I like to delete files with "delete" and memory with "delete" or "free". But
hopefully we don't need special functions to manage memory (use new and delete).
>
>* Do we agree that "Remove" always means dis-associating an object with
>some other object but not disposing of it?
How about "Unlink" instead? Remove sounds like delete to me.
>
>That's all I wanted to ask for now.
>
>BTW, how about a status report on the interpreter? I'd also be interested
>in a interpreter compiled to a library with APIs to add/remove commands (a
>simple command class that contains the command name and a Run() method),
>functions, constants etc. This way we could experiment with it a bit better.
The interpreter will eventually be packaged as a shared lib. This will make everyone
happy considering the GNU GPL-L.
I'll get a new interp out ASAP -- and as soon as Alain gives me the ASIP login info.
>
> Is here anybody who'd like to do a test compile of the block files on a
>PC, Unix or Linux compiler and tell us how it works etc.?
I have LinuxPPC to use. I'll use egcs on them. I already plan to before releasing the
next interpreter.
I can also try them on the dark side using Boreland 4.5 and cygwin (i.e., egcs).
>
> BTW, do we have a download area again? What do I have to do to upload
>XBlockFile there, and can I DL an interpreter snapshot there?
I'd love for Alain to answer that.
