Re: Happy christmas

"santosh" <santosh.k83@xxxxxxxxx> wrote in message

And this particular task is also doable in standard C with no loss in
functionality or efficiency. I understand that the Committee had an
overall policy to include only those new functions in the Standard
library that would be impossible or difficult to replicate in user
code. This is opposite to the philosophy of the C++ Committee.

It's not a good policy.
For instance everyone can knock up a strcpy() in a matter of minutes. You can even improve the ANSI version somewhat.
But if you are reading standard, workaday code, that is maybe manipulating a user report in a protein program, its a big help if the calls are familiar with you. You don't want to be distracted by

if( str_lsetsafe(fred, FREDLEN, jim, 0, -1) == ERRVAL)
goto genbufferror;

when all we're doing is setting fred equal to jim.


--
Free games and programming goodies.
http://www.personal.leeds.ac.uk/~bgy1mm

.

Relevant Pages

  • Re: Happy christmas
    ... the internet. ... functionality or efficiency. ... overall policy to include only those new functions in the Standard ... This is opposite to the philosophy of the C++ Committee. ...
    (comp.lang.c)
  • Re: Happy christmas
    ... functionality or efficiency. ... overall policy to include only those new functions in the Standard ... This is opposite to the philosophy of the C++ Committee. ... functionality or speed, then I'd use the platform specific version, ...
    (comp.lang.c)
  • Re: Happy christmas
    ... functionality or efficiency. ... This is opposite to the philosophy of the C++ Committee. ... It's not a good policy. ... standard appears to have lost sight of. ...
    (comp.lang.c)
  • Re: What could J4 (or WG4) do (was: INSPECT and TRAILING syntax
    ... my intent was "The reports of the demise of the COBOL *standards ... of time or resources to tackle what you suggest right now. ... If I was on this committee, ... Was the 2002 standard later than anybody wanted it to be? ...
    (comp.lang.cobol)
  • Re: what happened to hash-tables
    ... >> You already need hashtables anyway internally for implementing Common ... Many of the people on the committee had much more experience ... The ANSI standard is about memorializing the "Common" practice ... Suppose that the winning extensible hash table protocol is based ...
    (comp.lang.lisp)