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: 146b77,d275ffeffdf83655 X-Google-Attributes: gid146b77,public X-Google-Thread: f5d71,d275ffeffdf83655 X-Google-Attributes: gidf5d71,public X-Google-Thread: 103376,d275ffeffdf83655 X-Google-Attributes: gid103376,public X-Google-Thread: 109fba,d275ffeffdf83655 X-Google-Attributes: gid109fba,public From: "Fredric L. Rice" Subject: Re: Ada vs C++ vs Java Date: 1999/02/09 Message-ID: <36BF8BE4.93774F9E@linkline.com>#1/1 X-Deja-AN: 442242206 Content-Transfer-Encoding: 7bit References: <369C1F31.AE5AF7EF@concentric.net> <369DDDC3.FDE09999@sea.ericsson.se> <369e309a.32671759@news.demon.co.uk> <77ledn$eu7$1@remarQ.com> <77pnqc$cgi$1@newnews.global.net.uk> <8p64spq5lo5.fsf@Eng.Sun.COM> <77t3ld$nou$1@nnrp1.dejanews.com> <79ce4s$lfq$1@nnrp1.dejanews.com> <79chc7$ko6@drn.newsguy.com> <79dodb$rhf$1@nnrp1.dejanews.com> <79fm3e$ffs$1@nnrp1.dejanews.com> <79fnce$iv8@drn.newsguy.com> <79grbs$d5u$1@nnrp1.dejanews.com> <79hujb$ck3@drn.newsguy.com> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: The Skeptic Tank MIME-Version: 1.0 Newsgroups: comp.lang.ada,comp.lang.c++,comp.vxworks,comp.lang.java Date: 1999-02-09T00:00:00+00:00 List-Id: mike wrote: >For example, should a sort routine be standardized? >Probably not, there are so many different algorithms, and >different algorithms are appropriate for different >purposes, > But a standard sort package would only specify the interface, and > would leave the implementation up to the vendor. isn;t this how > things are supposed to be? That's how it's done in the C++ world. qsort() is the function that is normally called when a sort is desired and one must provide the guts of the function. Also, it's done in embedded C++ compilers with open(), read(), write(), and even fprintf(). The compiler vender creates those functions (which are linked as _open() _read() _write() et al.) and those in turn call a function that the engineer is supposed to supply (__open() __read() __write() et al. or some times _xopen() _xread() _xwrite() -- the vender will have a chapter covering elements of the embedded compiler which must be supplied by the software engineer.