ext portability question

[Ara.T.Howard]

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
===============================================================================

 

[nobu.nokada]

Hi,

At Tue, 22 Jun 2004 13:13:13 +0900,
Ara.T.Howard wrote in [ruby-talk:104311]:

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:

$ ruby18 -v -rmkmf -e 'have_struct_member("struct statfs", "f_blocks", "sys/statfs.h")'
ruby 1.8.2 (2004-06-19) [i686-linux]
checking for struct statfs.f_blocks... yes

 

[Ara.T.Howard]

Hi,

At Tue, 22 Jun 2004 13:13:13 +0900,
Ara.T.Howard wrote in [ruby-talk:104311]:

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:

$ ruby18 -v -rmkmf -e 'have_struct_member("struct statfs", "f_blocks", "sys/statfs.h")'
ruby 1.8.2 (2004-06-19) [i686-linux]
checking for struct statfs.f_blocks... yes

never knew about that one - guess i need to read mkmf! thanks.

-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
===============================================================================

 

[Daniel Berger]

i've got a little statfs ext which works fine.

See "filesystem" by Mike Hall. The RAA entry is outdated (Mike!) so
get the latest at http://users.rcn.com/m3ha11/ruby/ruby.html.

Regards,

Dan

 

[Ara.T.Howard]

See "filesystem" by Mike Hall. The RAA entry is outdated (Mike!) so
get the latest at http://users.rcn.com/m3ha11/ruby/ruby.html.

Regards,

Dan

thanks daniel - i checked this out but gave up on the dead link too soon.

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
===============================================================================

 

[Aredridel]

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?

Strongly in favor.

Ari