From: mrs@wrs.com (Mike Stump)
To: egcs@cygnus.com, scottm@cs.ucla.edu
Subject: Re: namespaces
Date: Fri, 05 Sep 1997 18:51:00 -0000 [thread overview]
Message-ID: <199709060151.SAA24232@kankakee.wrs.com> (raw)
> From: scottm@cs.ucla.edu
> To: egcs@cygnus.com
> Date: Fri, 5 Sep 1997 18:40:41 -0700 (PDT)
> Before someone says, "Why don't you work on it?", can I ask the
> simply obvious: What's the state of affairs of namespaces?
They don't work. That is the state. There is support in the parser
for all the syntax, and there are some functions relating to
namespaces in the compiler now, but it is reasonable to rip them all
out, and start from scratch. There are some tough choices to make,
how much memory to burn v how slow do you want the compiler...
next reply other threads:[~1997-09-05 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-05 18:51 Mike Stump [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-25 2:54 namespaces eziolkow
2002-04-25 2:56 ` namespaces Gerald Pfeifer
2002-04-25 3:13 ` namespaces Paolo Carlini
1998-05-08 19:52 namespaces Mike Stump
1997-11-29 5:43 namespaces Andrew Veliath
1997-11-29 15:18 ` namespaces Andrew Veliath
1997-09-05 18:40 namespaces scottm
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=199709060151.SAA24232@kankakee.wrs.com \
--to=mrs@wrs.com \
--cc=egcs@cygnus.com \
--cc=scottm@cs.ucla.edu \
/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).