Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!EU.net!sun4nl!fwi.uva.nl!not-for-mail From: casper@fwi.uva.nl (Casper H.S. Dik) Newsgroups: comp.unix.solaris,comp.unix.bsd.misc,comp.unix.internals Subject: Re: Solaris 2.6 Supersedes: <cancel.casper.32a7ec57@mail.fwi.uva.nl> Date: 6 Dec 1996 10:50:16 +0100 Organization: Sun Microsystems, Netherlands Lines: 34 Distribution: inet Message-ID: <casper.32a7ec57@mail.fwi.uva.nl> References: <32986299.AC7@mail.esrin.esa.it> <casper.32a3e5ae@mail.fwi.uva.nl> <580sgh$kpi@panix2.panix.com> <slrn5a983t.hgl.bet@onyx.interactive.net> <5844u3$mb@saltmine.radix.net> <587t33$2va@anorak.coverform.lan> NNTP-Posting-Host: mail.fwi.uva.nl Xref: euryale.cc.adfa.oz.au comp.unix.solaris:91562 comp.unix.bsd.misc:1693 comp.unix.internals:11474 brian@anorak.coverform.lan (Brian Somers) writes: >Nope - it's not possible to summarize the impossible. There are only >two ways to link old and new object files: > 1. Store, with each unresolved symbol in the object file, the > expected version of that symbol. This, of course, is totally > impractical. > 2. *NEVER* change a symbol declaration in a header file - just create > new ones and always support the old ones. This is both totally > impractical and completely insane. >Anyone got any other bright ideas ? Let's hear them. Go for "C++ style name mangling" for C. Now you can have both lseek's in your C library w/o any trouble. Oops, I guess we'll have to wait until C 9x comes out or whenever old style declarations and implicit declarations become illegal. BTW, how did BSD solve "ftell()"? Did they make a long 64 bits? (ftell() returns a *long*, not an off_t) Casper -- Casper Dik - Sun Microsystems - via my guest account at the University of Amsterdam. My work e-mail address is: Casper.Dik@Holland.Sun.COM Statements on Sun products included here are not gospel and may be fiction rather than truth.