From: "Ara.T.Howard" <Ara.T.Howard@...>
Date: 2004-06-22T13:13:13+09:00
Subject: ext portability question


i've got a little statfs ext which works fine.  the man page, however, claim
subtly different struct statfs layouts for different *nixes.  what is the
preferred method for dealing with this?  the struct is exposed to ruby via a
wrapped struct so the layout actual cannot be abstracted.  right now i am
considering:

   arch = Config::CONFIG['arch']

   case arch
     when /linux/
       spit_out_linux_src
     when /sun/
       spit_out_sun_src
     else
       spit_out_posix_src
   end

   create_makefile 'statfs'

in extconf.rb.

another question: these methods __really__ fit into the File class:

   File.statfs path

   file.statfs

how strongly are people opposed to this sort of standard class munging?

cheers.

-a
--
===============================================================================
| EMAIL   :: Ara [dot] T [dot] Howard [at] noaa [dot] gov
| PHONE   :: 303.497.6469
| A flower falls, even though we love it; and a weed grows, even though we do
| not love it. --Dogen
===============================================================================