9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: lucio@proxima.alt.za, 9fans@9fans.net
Subject: Re: [9fans] corrections to /sys/src/cmd/8l/l.h
Date: Wed, 30 Sep 2009 08:57:06 -0400	[thread overview]
Message-ID: <5bf8b5390a97a1ebaad1d77a2dcbb9a7@brasstown.quanstro.net> (raw)
In-Reply-To: <<4c83c9076f3de55d5a49deff52f0f37c@proxima.alt.za>>

On Wed Sep 30 00:30:19 EDT 2009, lucio@proxima.alt.za wrote:
> At the tail end of the module there is a shorter set of "#pragma
> varargck"s that repeats the entries earlier in the file, disagreeing
> with one of them.  The disagreeing entry matches the #pragma in
> /sys/src/cmd/vl/l.h so I'm not sure which ought to be used (or what
> effect the conflict has).
>

it's okay to have varargchk type's specify different types for the same
format letter, as long as each is valid.  for example, since uintptr and
void* are both valid arguments for #p, libc properly declares both okay.
in your case uint and int are both declared okay.  and it looks good
to me as the argument is used an index into a name array.  in fact,
due to c type promotion rules, one could also declare char, uchar,
short, ushort to be acceptable.  though evidently that's not needed.

duplicate entries should probablly deleted.  while you're at it, add
#pragma	varargck	argpos	diag		1

you will then be magicly informed of a few vararg botches.

- erik



       reply	other threads:[~2009-09-30 12:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<4c83c9076f3de55d5a49deff52f0f37c@proxima.alt.za>
2009-09-30 12:57 ` erik quanstrom [this message]
2009-09-30  4:27 lucio
2009-10-01 10:22 ` sqweek

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=5bf8b5390a97a1ebaad1d77a2dcbb9a7@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    --cc=lucio@proxima.alt.za \
    /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).