public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Laurent GUERBY <laurent@guerby.net>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: "Manuel López-Ibáñez" <lopezibanez@gmail.com>, gcc@gcc.gnu.org
Subject: Re: Notes from the GROW'10 workshop panel (GCC research   opportunities workshop)
Date: Thu, 22 Apr 2010 09:18:00 -0000	[thread overview]
Message-ID: <1271926978.22600.202.camel@pc2.unassigned-domain> (raw)
In-Reply-To: <20100415115737.GA32020@hector.lesours>

On Thu, 2010-04-15 at 13:57 +0200, Basile Starynkevitch wrote:
> (BTW I call lowlevel any language which does not manage memory
> automatically; I am quite fond of Ocaml even if I don't use it much today.
> So in my eyes C++, Ada95 & Fortran2005 are still low-level; this is only a
> matter of taste & terminology).

You didn't look very hard in the Ada Reference Manual :). 

Garbage collection support for Ada implementations is optional but
defined in Ada since the first standard in 1983.

All Ada standards (83/95/05) do have a "garbage collection" entry in
their index wich lists the various parts of the standard interacting
with absence or presence of automatic memory management, for example
see "pragma Controlled".

GNAT/GCC does not provide garbage collection but GNAT/dotnet and
GNAT/Java do provide it so you can run Ada software these days without
having to do manual memory management.

Sincerely,

Laurent



  parent reply	other threads:[~2010-04-22  9:03 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11 14:01 Dorit Nuzman
2010-04-11 18:27 ` Chris Lattner
2010-04-11 19:38   ` Grigori Fursin
2010-04-11 20:25     ` Chris Lattner
2010-04-11 20:58       ` Grigori Fursin
2010-04-14 14:34 ` Grigori Fursin
2010-04-14 14:58   ` Steven Bosscher
2010-04-14 15:21     ` Manuel López-Ibáñez
2010-04-14 15:30       ` Steven Bosscher
2010-04-14 15:36       ` Diego Novillo
2010-04-14 15:50         ` Nathan Froyd
2010-04-14 15:57           ` Richard Guenther
2010-04-14 19:19             ` Tom Tromey
2010-04-14 16:06           ` Diego Novillo
2010-04-14 18:30             ` Richard Guenther
2010-04-14 18:49           ` Toon Moene
2010-04-14 19:52             ` Basile Starynkevitch
2010-04-14 20:31               ` Toon Moene
2010-04-14 20:43               ` Toon Moene
2010-04-14 21:02               ` Ian Lance Taylor
2010-04-14 21:34                 ` Manuel López-Ibáñez
2010-04-15  8:26                 ` Basile Starynkevitch
2010-04-15  8:38                   ` Manuel López-Ibáñez
2010-04-15 12:03                     ` Basile Starynkevitch
2010-04-15 12:07                       ` Andrew Haley
2010-04-15 12:15                         ` Steven Bosscher
2010-04-15 12:17                           ` Andrew Haley
2010-04-22  9:18                       ` Laurent GUERBY [this message]
2010-04-14 21:04               ` Nathan Froyd
2010-04-14 19:42           ` Ian Lance Taylor
2010-04-14 15:44       ` Duncan Sands
2010-04-15  9:05   ` Manuel López-Ibáñez
2010-04-16 12:36     ` Grigori Fursin
2010-04-16 17:15       ` Manuel López-Ibáñez
2010-04-16 17:40         ` Grigori Fursin
2010-04-27 12:40         ` Grigori Fursin
2010-04-27 16:31           ` Manuel López-Ibáñez
2010-04-27 18:42             ` Grigori Fursin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1271926978.22600.202.camel@pc2.unassigned-domain \
    --to=laurent@guerby.net \
    --cc=basile@starynkevitch.net \
    --cc=gcc@gcc.gnu.org \
    --cc=lopezibanez@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).