Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@paralogos.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Chad Reese <kreese@caviumnetworks.com>, linux-mips@linux-mips.org
Subject: Re: Is there no way to shared code with Linux and other OSes?
Date: Sat, 22 Nov 2008 04:44:52 -0600	[thread overview]
Message-ID: <4927E2A4.5000702@paralogos.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0811221109330.29539@anakin>

Geert Uytterhoeven wrote:
> On Sat, 22 Nov 2008, Kevin D. Kissell wrote:
>   
>> [This should be good for some useless weekend flaming.]
>>     
>
> Yeah! ;-)
>
>   
>> Chad Reese wrote:
>>     
Don't blame Chad for this quote, it was me!
>> to move away from such arbitrary dogmatism.  The argument given for banning
>> typedefs altogether is that nested typedefs are confusing to programmers.  I
>>     
>
> I thought the main reason was that you can't have forward declarations of
> typedefs, while you can have for structs.
>   
That's a better argument than the one in the HTML version of 
Documentation/CodingStyle.txt that I had bookmarked (which was what I 
cited).  Interestingly, if I look at the *current* Linux 
Documentation/CodingStyle.txt for 2.6.28-rc6, the blanket interdiction 
of typedefs is no longer there!  Things *have* evolved, as I said they'd 
have to, to recognize 5 (a good Illuminati number) cases where typedefs 
are permitted.  Superficially, based on Chad's description (I admit that 
I haven't been reviewing his patches) the Cavium case would seem to fall 
into the first category. Is the MIPS Linux community now some kind of 
ultra-orthodox sub-sect of the Linux cult? ;o)

          Regards,

          Kevin K.

  reply	other threads:[~2008-11-22 10:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-22  8:31 Is there no way to shared code with Linux and other OSes? Chad Reese
2008-11-22  9:54 ` Kevin D. Kissell
2008-11-22 10:13   ` Geert Uytterhoeven
2008-11-22 10:44     ` Kevin D. Kissell [this message]
2008-11-22 15:35       ` Ralf Baechle
2008-11-22 19:08         ` Chad Reese
2008-11-24 13:14           ` Ralf Baechle
2008-11-24 17:52             ` Chad Reese

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=4927E2A4.5000702@paralogos.com \
    --to=kevink@paralogos.com \
    --cc=geert@linux-m68k.org \
    --cc=kreese@caviumnetworks.com \
    --cc=linux-mips@linux-mips.org \
    /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