On Fri, 2 Nov 2001, Jason Diamond wrote:
> Then we could have a "driver" for each platform that consisted of nothing
> but #include's of other .c files. Making a directory for each platform might
> be appropriate if we do this. I bet that most of the posix "platform" source
> files would be #include'ed into each of the more specific drivers.
But one big problem is you can't even name all the platforms! New
platforms appear all the time that you never heard of, and Parrot might
work perfectly well on them, but you don't even know of the platform's
existence at release time.
Certainly platform-specific files are needed sometimes, but I've not seen
anything that convinces me that a linux.c file does anything but open the
floodgates to a maintenance job of maintaining lots of nearly-identical
files.
--
Andy Dougherty [EMAIL PROTECTED]
Dept. of Physics
Lafayette College, Easton PA 18042
