Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Jan 2000 13:28:19 +0100
From:      Alexander Langer <alex@big.endian.de>
To:        obrien@FreeBSD.ORG
Cc:        ports@FreeBSD.ORG, current@FreeBSD.ORG
Subject:   Re: 4.0-release (ports) schedule
Message-ID:  <20000125132819.B7575@cichlids.cichlids.com>
In-Reply-To: <20000124120117.N81215@dragon.nuxi.com>; from obrien@NUXI.com on Mon, Jan 24, 2000 at 12:01:17PM -0800
References:  <200001241436.GAA23651@silvia.hip.berkeley.edu> <20000124103710.B75151@dragon.nuxi.com> <20000124205021.B24975@cichlids.cichlids.com> <20000124120117.N81215@dragon.nuxi.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake David O'Brien (obrien@NUXI.com):

> > I noticed that many ports are broken because the compiler handles
> > ANSI-C++ violations too strict.
> Not too strict -- to the ratified ISO-C++ specification.

Yes. Ok :-)

> Nope.  Those programs that aren't buildable aren't C++.  I will not break
> the C++ compiler to support them.

Ok, I understand this. Probably I wouldn't do this, too.

Though:
Often a simple change from

char *stuff;
[..]

stuff = mmap()... (fails)
to
stuff = (char *) mmap()... (works)

does the trick.

Enough on this topic.

Alex

-- 
I doubt, therefore I might be. 


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?20000125132819.B7575>