>How do you plan on doing this? Template specializations? AFAIK, MrCpp
>does not like template specializations.
Anthony,
no, I'm planning to do it the same way as it's already supported in
XEndianFile: A const global that you create for each struct (not for each
instance, for the definition) which lists the field types + another global
that contains the sizes in RAM for this particular machine. This is all my
code should need to pack/unpack a struct before/after writing it.
>As long as the API docs are done before we need to use the thing.
You'll have to live with the comments in the headers and source files for
starters, but they all adhere to takes/gives specification and thus this'll
be feasible with the occasional question on the list until I have finished
the API docs.
>We'll probably need a base something like this:
>
> struct FCError_Base {
> FCError_Base(char *source_file, int source_line);
> virtual ToText(string&);
> char *source_file;
> int source_line;
> };
Sounds fine, but we'll have to derive this from exception (C++'s standard
exception class) so we'll also catch bad_alloc exceptions etc. that the STL
throws.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
