🚀 go-pugleaf

In article <MEISSNER.90Aug1191316@osf.osf.org> meissner@osf.org (Michael Meissner) writes:

   Hmm, don't you care about compatibility with things like system calls?
   I imagine the grief people would get if the stat structure got
   rearranged because some OS jock added a byte field at the end of the
   structure?  Yes, extern "C" can be used, but it just means that there
   are even more things to worry about getting right.

If you don't declare the `stat' function inside `extern "C"', it won't
necessarily work right anyway.  Using:

extern "C"
{
#include <sys/stat.h>
}

seems entirely reasonable to me.

   Also, it would seem to me that reordering things across class
   boundaries is a really bad idea -- then subclassing and virtual
   functions would have no chance of working.

If it is not feasible to reorder members across class boundaries and still do
subclassing and virtual functions right then noone will try to do it in their
implementation.  That doesn't mean the standard should prevent people from
trying if they want to.
--
	Roland McGrath
	Free Software Foundation, Inc.
roland@ai.mit.edu, uunet!ai.mit.edu!roland