On Sep 18, 2006, at 1:46 AM, Une bue wrote:

> i'm writting c ext to ruby specifically for the Mac OS X platform.

If it is specifically and only for one platform, don't bother making  
the directory structure (or code structure) more complicated. If it  
is mostly platform agnostic separate that out and have the platform  
specific stuff either split out if it is big, or if not, separated  
with ifdefs (I say that only because even with platform specific  
files, a good portion of those files will be duplicate anyways (think  
includes, declarations, definition skeletons--everything but the meat)).

In other words, do the simplest thing that works, right now, for what  
you actually need... If you need to extend for a second platform  
someday, deal with it then.