Talk:C standard library

From Wikipedia, the free encyclopedia

This article is supported by the Wikipedia:WikiProject C++. Please visit the project page for more details on the project.

How is the article C standard library supposed to be distinguished from the article ANSI C standard library ? Should they be merged? Bevo 15:51, 2 Jan 2004 (UTC)

It turns out that Talk:ANSI C standard library has some discussion about how the two articles can co-exist. I am somewhat convinced. I suppose "standard" for this article just means whatever an implementation vendor makes available with the #include <xxx.h> syntax. Bevo 15:59, 2 Jan 2004 (UTC)

Don't have time at the moment (might later), but it'd pretty things up some if the header files mentioned at the bottom of this article were linked to the subsections of ANSI C standard library that list the basic functions in those headers. MrZaius


Much of the C standard library has been shown to have been well-designed.

I disagree with this comment, and I feel it is POV. Some other notable people, such as Steve Maguire (author of "Writing Solid Code"), disagree, citing things like cryptic function names, inconsistent order of arguments to functions (for instance, in some functions, the first argument is a file pointer, and in others, it's the last), and so on. Other points are more debatable, e.g., realloc can function as an allocator, reallocator, and deallocator, all in one -- some feel this is good, and some don't. I'd revise or omit the statement, but don't really know the best way to do so without using weasel words. - Furrykef 11:32, 16 Nov 2004 (UTC)

[edit] merge from C Run-Time Library

I'm proposing a merge from the C Run-Time Library to the C standard library.

The new text for "C standard library" would be something like this:

The C Run-Time Library includes routines which may help the compiler itself with the program at runtime. The code that initializes the process for the operating system, for example, before calling main() lives in the C Run-Time Library for a given vendor's compiler. The Run-Time Library code might help with other language feature implementations, like handling uncaught exceptions or implementing floating point code.

The C standard library only documents that the specific routines mentioned in this article (C standard library) are available, and how they behave. The compiler implementer might depend on additional implementation-level functions to be avaialble, and is likely to package both the their run-time library and the C standard library in the same module, since they're both likely to be needed by any program built with their toolset.

What do you think?

-- Mikeblas 23:37, 31 December 2005 (UTC)

With no objections, I've performed the proposed merge. -- Mikeblas 21:32, 8 January 2006 (UTC)

[edit] GTK+

In the section "ANSI Standard", it says the GNOME project developed the GTK+ graphics toolkit, whereas the GTK+ was created for GIMP project, and is (more than anything) a sister project to the GNOME project. After all, GTK+ stands for the GIMP Toolkit. I think it's a stretch to say that it is developed by the GNOME project.

I am pretty sure the same goes for Glib. I don't know if those are worth correcting, though.


Ibjt4ever 02:18, 4 September 2006 (UTC)

[edit] Template

I want to do a guide for strarg.h, but I need the C libraries template. Any help?