Talk:Runtime library

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
WikiProject Computing (Rated Start-class, Low-importance)
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 Low  This article has been rated as Low-importance on the project's importance scale.
 

Unnamed section[edit]

I propose merging this article with runtime system, which does a good job of explaining what a runtime library is and does. A runtime library is the API exposed by a runtime system. — Preceding unsigned comment added by Seanhalle (talkcontribs) 16:14, 29 April 2013 (UTC)

Untitled[edit]

I really thank you, the author of this article which is the only definition and explanation of "Runtime Library" I can find in the whole world wide web.

But I'm sorry, I still don't get it.

Your definition of "Runtime Library" is,

- "a runtime library is a special program library used by a compiler to implement functions built into a programming language during the runtime (execution) of a computer program. "

What is done during the runtime? Implementing functions? Building functions into a programming language?

Could anyone show a example?

- Daniel Kang.

I too stumbled across this introductory definition. I think it is not correct.
"[...] a runtime library is a special program library used by a compiler [...] during the runtime (execution) of a computer program." This sentence is wrong imho. A compiler is only "active" on a program during compile time in order to generate machine code (among other things). When the compile time is over and the program is executed (this is runtime) the compiler is no more active.
The same misunderstandings apply to the following sentence: Many programming languages have built-in functions that do not necessarily have to be realized in the compiler, but can be implemented in the runtime library.
Shouldn't it read by the compiler?
--Abdull (talk) 19:25, 7 February 2008 (UTC)


Well it's correct...though it should be explained in a clearer fashion.
Basically, unless I'm completely off the mark in abusing language here, we're talking about the "linker runtime" if you will.
Such as under linux were the linker calls the CRT( C Run Time ) libraries. (example from the GCC's linker process: http://www.network-theory.co.uk/docs/gccintro/gccintro_87.html)
Here are the CRTs under windows as well: http://msdn.microsoft.com/en-us/library/abx4dbyh.aspx
Basically the runtime libraries are the libraries that are accessed by the linker regardless if they statically or dynamically linked, and are expected to be present every time the compiler is run. libc for instance, is always expected to have some form of implementation when a C compiler is run. Any other library not expected to be available(ie. the OGL libs) cannot be considered a run-time library.
I would appreciate further input backing me up on this before I touch it, but what I'm saying seems to be well summarised in the intro for the C standard library article.
--Danukasan (talk) 08:28, 27 June 2009 (UTC)


This can be a good article but at the moment is somewhat confusing. The boundaries of what is a runtime library is not clearly defined. Bringing some clear examples would help.


If I understand what the article tries to say, a runtime library is all the functionality behind core language features, like FOR loops, IF statements, functions, structures, classes, etc. All those language construct have to be converted to the functionality they represent, and the runtime library is where all that functionality is.
Which is not the same as a normal language library like the C or C++ standard library because those are not core language features, i.e they are built upon the language itself, which in turn is bulit upon the runtime library.
Am I correct? — Preceding unsigned comment added by Hrgwea (talkcontribs) 13:43, 29 December 2013 (UTC)

Hello there! You're right, the article was slightly confusing. I've edited the article so it should provide a better explanation, please check it out. Makes more sense now? — Dsimic (talk) 00:53, 30 December 2013 (UTC)

I still don't get it.[edit]

Can you tell us like we are totally new to the world of programming.Lounes653 (talk) 02:30, 21 December 2007 (UTC)

Contradictions[edit]

The article first says "For example, the programming language C requires only a very minimal runtime library, but defines a large standard library (called C standard library) that each implementation has to deliver." but then gives as examples of C runtime libraries the Microsoft ones, which definitely belong to the second class (large standard library).TorLillqvist (talk) 21:01, 10 August 2009 (UTC)