Date: Tue, 17 Feb 1998 12:18:24 +0200 (SAT) From: Robert Nordier <rnordier@iafrica.com> To: rssh@grad.kiev.ua Cc: freebsd-ports@FreeBSD.ORG Subject: Re: ANNOUNCE: TenDRA C/C++ compiler (fwd) Message-ID: <199802171018.MAA14957@eac.iafrica.com> In-Reply-To: <34E81835.575C6296@Shevchenko.kiev.ua> from Ruslan Shevchenko at "Feb 16, 98 12:43:06 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
[Cc list trimmed]
Ruslan Shevchenko wrote:
> Robert Nordier wrote:
> > Actually, no. One of the main design features of TenDRA is that you
> > *don't* have to modify system headers (you modify API definitions
> > instead). This means you can write (say) SVID3 programs, even if your
> > libraries aren't particularly SVID compatible. (I just compiled a
> > whole bunch of UNIX95 API programs, even though FreeBSD's UNIX95 API
> > support is rather limited.)
> >
>
> Problem not in API, but in language: 1. wchar_t must not be defined when we
> use headers in __cplusplus mode by
> TenDRA.
> (on SCO_SV it was the main problem)
> 2. The same with bool
> 3. all variables must have linked type.
> 4. empty blocks in C++ {}; now is illegal, I'm not shure,
> is our _BEGIN_DECL and _END_DECL do the correct things.
You may be right regarding C++ problems (I'm using the compiler
for portability-checking some C work, so that's all my experience
for now).
For the C APIs, you can actually
rm -fr /usr/include
completely, and this won't affect anything: you just have to add
stuff like
#define __WRONG_XPG3_FTW_H
to the library startup definitions during porting, if you don't
have a correct (or parseable, or any) ftw.h file.
Being able to ignore system headers can be particularly useful, as
most OS vendors tend to support multiple APIs very badly.
--
Robert Nordier
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802171018.MAA14957>