Rum-Time Library vs Standard Library

[Carmen Sei]

what are the difference between

Rum-Time Library vs Standard Library

http://msdn2.microsoft.com/en-us/library/cscc687y(VS.80).aspx
http://msdn2.microsoft.com/en-us/library/59ey50w6(VS.80).aspx

 

[Tristan Wibberley]

what are the difference between

Rum-Time Library vs Standard Library

The standard library is a particular set of defined names and headers as
defined in the C++ standard document, a runtime library is a blob of
binary stuff that is used as a part of the compiled program but is not
included in your program executables because it is so commonly needed.
Instead, those pieces of functionality are included on the host machine
(although you might need to ask your customers to install an updated
runtime if they have an older service pack) so they get included into
your program only at "runtime".

--
Tristan Wibberley

Any opinion expressed is mine (or else I'm playing devils advocate for
the sake of a good argument). My employer had nothing to do with this
communication.

 

[Paavo Helde]

what are the difference between

Rum-Time Library vs Standard Library

http://msdn2.microsoft.com/en-us/library/cscc687y(VS.80).aspx
http://msdn2.microsoft.com/en-us/library/59ey50w6(VS.80).aspx

The first one is C++ Standard Library, which is C++ specific. The second is
C run-time library, which is used by both C and C++ programs and most
probably also by the C++ standard library.

hth
Paavo

 

[Rahul]

what are the difference between

Rum-Time Library vs Standard Library

http://msdn2.microsoft.com/en-us/li...rosoft.com/en-us/library/59ey50w6(VS.80).aspx

Many vendors implement c++ standard library as a runtime library... so
that they get linked dynamically into the program, it makes sure that
the size of the executable is less...

Moreover, if the vendor provides a next version of the standard
library, the developer wouldn't need to re-link his program, instead
can directly run the executable...the linking in this case would be
taken care by dynamic linker/loader...

 

[James Kanze]

The standard library is a particular set of defined names and
headers as defined in the C++ standard document, a runtime
library is a blob of binary stuff that is used as a part of
the compiled program but is not included in your program
executables because it is so commonly needed.

You make it sound as if a runtime library must be dynamically
linked. That's not true---in the past, they were almost always
statically linked (if only because the systems back then didn't
support dynamic linking), and even today, you typically have a
choice.

I don't know if there is actually any formal definition of
runtime library. I've certainly seen it used in the sense of
any library for which you don't have the source code (or don't
use the source code, if it's open source). I think I've also
seen it used in a more restrictive sense, as the library which
provides the direct interface to the OS. And it's frequently
used to refer to the "bundled" libraries: those that are always
present on the machine (or delivered with the compiler).

FWIW: I'm not even sure that "runtime library" always refers to
a library. On early Unix, it was common to refer to crt0.o as
the runtime library, although it was an object file, and not a
library. (The "crt" in the name was for "C Run Time", and the 0
because it was the first thing run, before your own code.)