Return to BSD News archive
Xref: sserve comp.windows.x.i386unix:10943 comp.os.386bsd.apps:1328 comp.os.386bsd.questions:12063 Newsgroups: comp.windows.x.i386unix,comp.os.386bsd.apps,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!yeshua.marcam.com!charnel.ecst.csuchico.edu!csusac!csus.edu!netcom.com!bakul From: bakul@netcom.com (Bakul Shah) Subject: Re: __NetBSD__ X11R6 i386 Message-ID: <bakulCtzKKE.MA2@netcom.com> Organization: NETCOM On-line Communication Services (408 261-4700 guest) References: <30dr4j$phk@darum.uni-mannheim.de> <bakulCtsIBF.4BH@netcom.com> <31mgdu$s9d@news.rhrz.uni-bonn.de> <deeken.775902001@iti.informatik.th-darmstadt.de> <31nqad$mii@news.rhrz.uni-bonn.de> Date: Thu, 4 Aug 1994 01:09:50 GMT Lines: 36 juengst@saph2.physik.uni-bonn.de (Henry G. Juengst) writes: >To say 'bring it into imake's scope' and to say 'use the include file >of the OS' is not the same. The first one could also mean, that one uses >his/her/its private - proper - declaration. That's what happens in many >applications. It is not ok to declare a foreign identifer in your own >source file. The only compatible way is to include the required header >files of the foreign software. Whan I said ``bring it into imake's scope'' I meant just that; I assumed the person who asked the question was savvy enough to figure out the best way of doing it. Just as you later pointed out, complete OS specific include files don't always exist. It is not a ``good practice'' to use your own declarations; one should always use standard headers files if possible but it is perfectly legitimate to use own your declarations. Just ask your compiler!! >Anyway, the imake specific problem is in the ftruncate function call, >but the previous statement is also true for this one. Right. I forgot. >I'm pissed off by all those sys_errlist, lseek etc. declarations in too >many programs. I know that there are some poor systems without complete >OS specific header files, but for those chests one could declare the >missing identifiers between #ifdef osname ... #endif. What is done in too many other programs is entirely irrelevant to what the original poster was asking about. At any rate, don't take it out on me because you are pissed about something. I was only trying to help. You could've gotten your point across without flaming by saying something like ``make sure you use the right include file instead of declaring it in the source file''.