9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] type signatures
Date: Tue,  3 Mar 2009 00:42:11 +0000	[thread overview]
Message-ID: <368d2b2234e3869e64c2d6c45c53b878@terzarima.net> (raw)
In-Reply-To: <307e6ea2aed293668f8a7caacb1b5e2b@quintile.net>

[-- Attachment #1: Type: text/plain, Size: 99 bytes --]

that seems correct. if you want an incomplete type, you can specify that
(with pragma incomplete).

[-- Attachment #2: Type: message/rfc822, Size: 2160 bytes --]

From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: [9fans] type signatures
Date: Mon, 2 Mar 2009 15:23:01 +0000
Message-ID: <307e6ea2aed293668f8a7caacb1b5e2b@quintile.net>

Hi,

I get a different type sygnature depending on weather the arg to a function
contains members which are in scope or not - is this expected or a bug?

for example:

/* junk.c */
typedef struct unknown unknown;
#ifdef DEF
struct unknown {
	int a;
};
#endif

typedef struct arg arg;
struct arg {
	unknown *u;		// Note pointer, not instance
};

void
func(arg a)
{
	USED(a);
}

larch% 8c -T t.c && nm -T junk.8
b0b8ed37  T func
larch% 8c -T -DDEF t.c && nm -T junk.8
763b103c  T func

-Steve

  parent reply	other threads:[~2009-03-03  0:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 15:23 Steve Simon
2009-03-02 15:40 ` Fco. J. Ballesteros
2009-03-02 20:05   ` Steve Simon
2009-03-03  0:42 ` Charles Forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-19  0:45 erik quanstrom

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=368d2b2234e3869e64c2d6c45c53b878@terzarima.net \
    --to=forsyth@terzarima.net \
    --cc=9fans@9fans.net \
    /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).