Re: 10 most used

From: Joona I Palaste (palaste_at_cc.helsinki.fi)
Date: 05/30/04 

Date: 30 May 2004 18:33:30 GMT

Profetas <xuxu_18@yahoo.com> scribbled the following:
>>In 'comp.lang.c', windle@charter.net wrote:
>>>>>Hi I am starting a project in C.
>>>>>And I would like to hear from you the 10 most used c library.
>>>>>
>>>>>just say the ones that pop up in your head.
>>>>
>>>> stdlib.h
>>
>>>stdlib.h is far to be a library. It's just an emerging part of the
> standard C
>>>library. It's a user interface.

>>Sorry, I misunderstood his question.

> That is what I ment the ones that I use is
> malloc.h
> string.h
> stdio.h

> I want the ones that you use that I have not listed above.

malloc.h is non-standard, needless and probably deprecated as well. All
its functionality can be found in stdlib.h. 

-- 
/-- Joona Palaste (palaste@cc.helsinki.fi) ------------- Finland --------\
\-- http://www.helsinki.fi/~palaste --------------------- rules! --------/

Relevant Pages

  • RE: [perfmon] Re: quick overview of the perfmon2 interface
    ... Tools into a standard mold... ... Just crippling flexibility/cutting functionality ... - Tools need to port to Perfmon with min cost. ... - Allow OS data correlated to PMU ...
    (Linux-Kernel)
  • Re: Non-standard arithmetic
    ... to all intuition -- every property of all standard naturals ... automatically carries over to all non-standard naturlals. ... (with additional axioms to define/distinguish standard and non- ...
    (sci.logic)
  • Re: INSPECT and TRAILING syntax
    ... adding new syntax is a POST-2002 development. ... '02 Standard was that it was simply "TOO BIG". ... COULD already be accomplished and did the language really need them. ... the syntax for that functionality is pretty straightforward -- adds ...
    (comp.lang.cobol)
  • Re: Clunky C cleanup code
    ... some 'portability' for functionality. ... The C-Standard is not the ... the program reports successful termination. ...
    (comp.lang.c)
  • Re: Automatically generate variables
    ... if the question was "how much of the program is standard C?" ... that it's just as non-standard as my version. ... If the non-standard header has no impact on the rest of the file then only that one line is "pseudo-C crap", if you don't know the contents of the header then the entire presented code can validly be considered as "pseudo-C crap". ...
    (comp.lang.c)