From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10a146,a03ae7f4e53958e1 X-Google-Attributes: gid10a146,public X-Google-Thread: fac41,a03ae7f4e53958e1 X-Google-Attributes: gidfac41,public X-Google-Thread: 103376,8775b19e3c68a5dc X-Google-Attributes: gid103376,public X-Google-Thread: 1014db,a03ae7f4e53958e1 X-Google-Attributes: gid1014db,public X-Google-Thread: 109fba,a03ae7f4e53958e1 X-Google-Attributes: gid109fba,public X-Google-Thread: 1094ba,a03ae7f4e53958e1 X-Google-Attributes: gid1094ba,public X-Google-Thread: 114809,a03ae7f4e53958e1 X-Google-Attributes: gid114809,public X-Google-Thread: fa0ae,a03ae7f4e53958e1 X-Google-Attributes: gidfa0ae,public From: Ian Piumarta Subject: Re: Which language pays most? Smalltalk, not C++ nor Java. Date: 1998/01/02 Message-ID: #1/1 X-Deja-AN: 312220537 Content-Transfer-Encoding: 8bit References: <199712121931.LAA25389@sirius.infonex.com> <34AC5A07.383C4AE3@acm.org> <68jd83$ogs$2@darla.visi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Organization: INRIA-Rocquencourt Newsgroups: comp.lang.fortran,comp.lang.c,comp.lang.c++,comp.lang.eiffel,comp.lang.java.programmer,comp.lang.smalltalk,comp.lang.perl.misc,comp.lang.ada,comp.edu Date: 1998-01-02T00:00:00+00:00 List-Id: firewind writes: > Hmm... the 'C Extensions' section of the gcc Info pages seem pretty > complete and decently detailed to me. Is there something I don't know? :) Some of the extensions don't work on all architectures; e.g. global register variables (and the associated -ffixed and -fcall-used compiler options) were broken in gcc for PowerPC/RS6000 the last time I checked. Some of the extensions also break documented behaviour in other ways; e.g. first-class labels and the compiler options to enable coverage testing (-a -ftest-coverage -fprofile-arcs) do not mix well (presumably because the compiler can't figure out exactly where an "arc" from a "computed goto" goes to ;). Unfortunately (at least for language implementors) some of the gcc extensions are crucial to achieving good performance. For gcc and public-domain source code, at least, I agree with the poster who suggested the pragmatic approach of declaring with which compiler the code compiles successfully, and leaving it at that. (In commercial situations I can accept that "responsible programming behaviour" might be very different.) Ian