Date: Mon, 5 May 1997 14:45:10 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: terry@lambert.org, bde@zeta.org.au, nadav@barcode.co.il, hackers@FreeBSD.ORG Subject: Re: /usr/include/ftpio.h is not C++ safe Message-ID: <199705052145.OAA16806@phaeton.artisoft.com> In-Reply-To: <7866.862868211@time.cdrom.com> from "Jordan K. Hubbard" at May 5, 97 02:36:51 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > How can libftpio be used by code which must be compiled -traditional, > > without __P()? > > And why would you want to compile libftpio with -traditional? > I read the paragraph where you say: > > In addition, there are cases where old code must be compiled with > the -traditional flag (I think this is what Bruce was meaning here) > because of existing calling conventions in the code, and the lack > of a prototype in scope at the time of inter-object calling in the > old code itself. > > And I still don't see where this is applicable in this case at all. You're still missing my (and I think Bruce's) meaning here. I *don't* want to compile libftpio -traditional. I want to add "#include ftpio.h" and link libftpio to an older application which must be compiled -traditional. To do that, the header must be compilable with -traditional (ie: it needs __P()). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705052145.OAA16806>