9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Joel C. Salomon" <joelcsalomon@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] scopes in kencc
Date: Thu, 26 Apr 2007 21:12:36 -0400	[thread overview]
Message-ID: <7871fcf50704261812o6379c087xdfa8b74e6fa4adf2@mail.gmail.com> (raw)

I'm tracing through how the symbol table in kencc is maintained, and
I'm not finding the part where scopes are maintained.

E.g., when the compiler sees the declaration of *t in

	typdef int t;
	t foo;

	struct bar
	{
		int *t;
	};

where is it determined that LNAME is returned when *t is scanned
rather than LTYPE (the way it is returned in the declaration of foo)?

--Joel


             reply	other threads:[~2007-04-27  1:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27  1:12 Joel C. Salomon [this message]
2007-04-27  2:04 ` Russ Cox
2007-04-27  2:48   ` Joel C. Salomon
2007-04-27  3:02     ` Russ Cox
2007-04-27  4:35       ` Joel C. Salomon

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=7871fcf50704261812o6379c087xdfa8b74e6fa4adf2@mail.gmail.com \
    --to=joelcsalomon@gmail.com \
    --cc=9fans@cse.psu.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 NNTP newsgroup(s).