9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 8c question
Date: Fri,  8 Jul 2005 20:40:34 +0100	[thread overview]
Message-ID: <e5046d0e01e534127565c8fcb03b029c@terzarima.net> (raw)
In-Reply-To: <f4e875772b165f384f8dd867dc1819b0@plan9.bell-labs.com>

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

talk about making something simple as bizarre as possible.
that include file is just amazing, quite remarkable.

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

From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 8c question
Date: Fri, 8 Jul 2005 15:03:12 -0400
Message-ID: <f4e875772b165f384f8dd867dc1819b0@plan9.bell-labs.com>

On Fri Jul  8 10:37:10 EDT 2005, rminnich@lanl.gov wrote:
> 
> 
> On Thu, 7 Jul 2005, Russ Cox wrote:
> 
> > Nonsense.  There are plenty of typedefs in Linux.
> 
> for scalar types, sure. They're all over the place. Did you look any 
> deeper than the grep | wc?
> 
> What is being proposed is a typedef for something that might or might not 
> be a struct, depending on architecture. I'll be interested to see if that 
> flies. Go for it.
> 
> ron

There are actually more 'struct' typedefs in the linux header files
than Russ found in the .c files:

ethel% pwd
/n/other/jmk/linux-2.6.9/include
ethel% grep 'typedef.*{' */*.h|wc 
   1351    5593   62194
ethel% 

e.g. linux/spinlock.h:

#if (__GNUC__ > 2)
  typedef struct { } spinlock_t;
  #define SPIN_LOCK_UNLOCKED (spinlock_t) { }
#else
  typedef struct { int gcc_is_buggy; } spinlock_t;
  #define SPIN_LOCK_UNLOCKED (spinlock_t) { 0 }
#endif

  reply	other threads:[~2005-07-08 19:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01 23:17 Tim Newsham
2005-07-02 12:43 ` Charles Forsyth
2005-07-05  2:36   ` David Leimbach
2005-07-05 14:47     ` Ronald G. Minnich
2005-07-05 15:27     ` Latchesar Ionkov
2005-07-05 15:33       ` Ronald G. Minnich
2005-07-05 18:33         ` Tim Newsham
2005-07-05 15:35       ` David Leimbach
2005-07-07 23:08         ` Charles Forsyth
2005-07-08  0:06           ` Ronald G. Minnich
2005-07-08  0:27             ` Russ Cox
2005-07-08 14:36               ` Ronald G. Minnich
2005-07-08 19:03                 ` jmk
2005-07-08 19:40                   ` Charles Forsyth [this message]
2005-07-09  1:02                   ` Ronald G. Minnich
2005-07-08  3:31           ` Tim Newsham
2005-07-08 11:14             ` Charles Forsyth
2005-07-09  1:04             ` Tim Newsham
2005-07-09  9:40               ` Charles Forsyth
2005-07-11  0:57                 ` Ronald G. Minnich
2005-07-11  1:26                   ` [9fans] Xen comms Tim Newsham
2005-07-11 19:21                     ` Eric Van Hensbergen
2005-07-11 19:23                   ` [9fans] 8c question Eric Van Hensbergen
2005-07-11 19:58                     ` Ronald G. Minnich
2005-07-11 20:05                       ` Eric Van Hensbergen
2005-07-11 20:15                         ` Ronald G. Minnich
2005-07-11 20:35                           ` Eric Van Hensbergen
2005-07-11 20:38                             ` Ronald G. Minnich
2005-07-11 21:03                               ` Eric Van Hensbergen
2005-07-11 21:09                                 ` Ronald G. Minnich
2005-07-11 21:13                                   ` Eric Van Hensbergen

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=e5046d0e01e534127565c8fcb03b029c@terzarima.net \
    --to=forsyth@terzarima.net \
    --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).