Joerg Sonnenberger wrote:
The first part was to separate the exported part of FILE from the internals to allow us to change the internals at will. It also broke a Ruby extension, which insists in taking the size of FILE, but that's something I don't care about.
It *is* evil to fiddle around with FILE and not FILE* objects, still programs are doing this (and might fail more or less silent). FreeBSD worked around this by indirecting private data into a private allocated struct. Can we build something to error out if somebody does a sizeof(FILE)?
cheers simon -- Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\ Work - Mac +++ space for low $$$ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
