Sujet : Re: Command Languages Versus Programming Languages
De : commodorejohn (at) *nospam* gmail.com (John Ames)
Groupes : comp.unix.shell comp.unix.programmer comp.lang.miscDate : 01. Apr 2024, 21:44:57
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <20240401134457.000067f2@gmail.com>
References : 1 2 3 4
User-Agent : Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
On Mon, 1 Apr 2024 11:15:52 -0700
John Ames <
commodorejohn@gmail.com> wrote:
And while this is pretty true of scripting languages, it doesn't make
for a good point-of-contrast with "non-scripting" languages; *piles*
of them include support for automatic memory management, and some
(outside of the C family) don't even include facilities for doing it
"by hand."
And, in fact, C actually does one specific bit of automatic memory
management itself - the stack, which may or may not even *be* a true
hardware stack (depending on the architecture,) and which is handled in
an entirely transparent fashion* by compiler-generated entry/exit code
generated by the compiler for each function.
* (Until you go and pass a pointer to a local variable to some piece of
code that expects it to still be valid later, natch.)