From owner-freebsd-current Fri Nov 22 15:30:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA26800 for current-outgoing; Fri, 22 Nov 1996 15:30:13 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA26738 for ; Fri, 22 Nov 1996 15:29:42 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA09574 for ; Sat, 23 Nov 1996 00:29:34 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA01678 for freebsd-current@FreeBSD.org; Sat, 23 Nov 1996 00:29:34 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id AAA29000 for freebsd-current@FreeBSD.org; Sat, 23 Nov 1996 00:11:37 +0100 (MET) From: J Wunsch Message-Id: <199611222311.AAA29000@uriah.heep.sax.de> Subject: Re: cdrom boot? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 23 Nov 1996 00:11:37 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611222115.OAA15993@phaeton.artisoft.com> from Terry Lambert at "Nov 22, 96 02:15:07 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > Isn't there unprotoize in the gcc distribution that does this? > I think you are thinking of "protoize". I think there might be an > unprotoize, but I think the idea of the GCC crowd is to move toward > ANSI code, not away. Well, thinking doesn't exactly seem to be your best task these days, Terry? :-)) protoize(1) used to be accompanied by unprotoize(1) in the gcc distribution for a long time. They use the gcc parser with a special shortcut that causes it to dump its internal structures in a C notation. > Depending on the compiler and the code, you may see problems with > const, volatile, and structure assignments. There are also problems > with agregate initialization of structure arrays (it works in K&R using > "{" based scoping, but fails in GCC). You forgot the split strings. Something like char foo[] = "This should \x1b" "creset your ANSI terminal.\n"; ...which couldn't be expressed unambiguously in pre-ANSI C. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)