public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: ricknu-0@student.ltu.se
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Vadim Lobanov <vlobanov@speakeasy.net>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Shorty Porty <getshorty_@hotmail.com>,
	Peter Williams <pwil3058@bigpond.net.au>
Subject: Re: [RFC][PATCH] A generic boolean (version 2)
Date: Thu, 20 Jul 2006 21:34:45 -0400	[thread overview]
Message-ID: <44C02F35.4000604@garzik.org> (raw)
In-Reply-To: <1153445087.44c02cdf40511@portal.student.luth.se>

ricknu-0@student.ltu.se wrote:
> diff --git a/include/asm-i386/types.h b/include/asm-i386/types.h
> index 4b4b295..841792b 100644
> --- a/include/asm-i386/types.h
> +++ b/include/asm-i386/types.h
> @@ -1,6 +1,13 @@
>  #ifndef _I386_TYPES_H
>  #define _I386_TYPES_H
>  
> +#if defined(__GNUC__)
> +typedef _Bool bool;
> +#else
> +#warning You compiler doesn't seem to support boolean types, will set 'bool' as
> an 'unsigned int'
> +typedef unsigned int bool;
> +#endif
> +
>  #ifndef __ASSEMBLY__
>  
>  typedef unsigned short umode_t;

Just delete the #ifdef and assume its either gcc, or a compatible 
compiler.  That's what we assume with other data types.


> @@ -10,6 +17,8 @@ typedef unsigned short umode_t;
>   * header files exported to user space
>   */
>  
> +typedef bool __u1;
> +
>  typedef __signed__ char __s8;
>  typedef unsigned char __u8;
>  
> @@ -36,6 +45,8 @@ #define BITS_PER_LONG 32
>  #ifndef __ASSEMBLY__
>  
>  
> +typedef bool u1;
> +
>  typedef signed char s8;
>  typedef unsigned char u8;
>  

I wouldn't bother with these types.  Nobody uses creates in their own 
hand-crafted bool uses, so I don't think people would suddenly start.


> diff --git a/include/linux/stddef.h b/include/linux/stddef.h
> index b3a2cad..498813b 100644
> --- a/include/linux/stddef.h
> +++ b/include/linux/stddef.h
> @@ -10,6 +10,9 @@ #else
>  #define NULL ((void *)0)
>  #endif
>  
> +#define false	((0))
> +#define true	((1))

I would say:

#undef true
#undef false
enum {
	false	= 0,
	true	= 1
};

#define false false
#define true true


  reply	other threads:[~2006-07-21  1:34 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 20:38 [RFC][PATCH] A generic boolean ricknu-0
2006-07-19 21:04 ` Jeff Garzik
2006-07-19 23:17   ` ricknu-0
2006-07-20  0:13     ` Jeff Garzik
2006-07-20  3:04       ` Vadim Lobanov
2006-07-20  3:53         ` Shorty Porty
2006-07-20  3:59           ` Dmitry Torokhov
2006-07-20  8:07           ` Jan Engelhardt
2006-08-04 14:03   ` Jes Sorensen
2006-08-04 14:42     ` Alan Cox
2006-08-04 14:35       ` Jes Sorensen
2006-08-04 15:51         ` Alan Cox
2006-08-04 15:58           ` Jes Sorensen
2006-08-04 16:00             ` Andreas Schwab
2006-08-04 16:08               ` Jes Sorensen
2006-08-04 16:16                 ` Andreas Schwab
2006-08-04 16:26                   ` Jes Sorensen
2006-08-04 16:57                     ` Andreas Schwab
2006-08-04 18:47                       ` Jes Sorensen
2006-08-04 18:51                         ` H. Peter Anvin
2006-08-04 18:58                           ` Jes Sorensen
2006-08-04 19:04                             ` H. Peter Anvin
2006-08-06  9:25                   ` Jan Engelhardt
2006-08-06  9:48                     ` Andreas Schwab
2006-08-06  9:31                 ` Jan Engelhardt
2006-08-06 15:31                   ` Jes Sorensen
2006-08-04 16:30             ` Alan Cox
2006-08-04 16:20               ` Jes Sorensen
2006-07-19 21:20 ` Alexey Dobriyan
2006-07-19 22:47   ` ricknu-0
2006-07-19 23:52     ` Peter Williams
2006-07-20  0:08       ` ricknu-0
2006-07-20  8:09   ` Jan Engelhardt
2006-07-21  1:24 ` [RFC][PATCH] A generic boolean (version 2) ricknu-0
2006-07-21  1:34   ` Jeff Garzik [this message]
2006-07-21  8:55     ` Pekka Enberg
2006-07-21 21:14       ` Jeff Garzik
2006-07-25 19:04         ` Roman Kononov
2006-07-21 22:31     ` ricknu-0
2006-07-23 19:56     ` ricknu-0
2006-07-21 14:23   ` Jan Engelhardt
2006-07-21 18:27     ` Michael Buesch
2006-07-21 21:14       ` Jeff Garzik
2006-07-21 22:11         ` ricknu-0
2006-07-22  8:56       ` Jan Engelhardt
2006-07-21 23:08 ` [RFC][PATCH] A generic boolean (version 3) ricknu-0
2006-07-21 23:27 ` ricknu-0
2006-07-22  5:40   ` Stefan Richter
2006-07-22 17:08     ` ricknu-0
2006-07-22 18:08       ` Stefan Richter
2006-07-22  8:58   ` Jan Engelhardt
2006-07-22 17:19     ` ricknu-0
2006-07-22  9:55   ` Lars Gullik Bjønnes
2006-07-23 15:43     ` ricknu-0
2006-07-23 15:49 ` [RFC][PATCH] A generic boolean (version 4) ricknu-0
2006-07-23 16:08   ` Jan Engelhardt
2006-07-23 19:36     ` ricknu-0
2006-07-23 20:26       ` Jeff Garzik
2006-07-23 20:25     ` Jeff Garzik
2006-07-23 21:17       ` Jan Engelhardt
2006-07-23 21:44         ` Jeff Garzik
2006-07-24  8:55     ` Paul Jackson
2006-07-23 16:13   ` Michael Buesch
2006-07-23 19:46     ` ricknu-0
2006-07-23 20:24   ` Jeff Garzik
2006-07-23 21:13   ` Paul Jackson
2006-07-25 23:22 ` [RFC][PATCH] A generic boolean (version 5) ricknu-0
2006-07-26  0:42   ` Paul Jackson
2006-07-26 20:28 ` [RFC][PATCH] A generic boolean (version 6) ricknu-0
2006-07-27  1:06   ` Paul Jackson
2006-07-27  2:10     ` Josef Sipek
2006-07-27  3:51       ` ricknu-0
2006-07-27  4:40         ` Josef Sipek
2006-07-27  4:00       ` Paul Jackson
2006-07-27  3:30     ` ricknu-0
2006-07-28 16:57     ` Jan Engelhardt
2006-07-27  2:48   ` Arnd Bergmann
2006-07-27  3:22     ` ricknu-0
2006-07-27  5:27     ` Nicholas Miell
2006-07-27  6:51       ` Paul Jackson
2006-07-27 19:55       ` ricknu-0
2006-07-27 20:13         ` Nicholas Miell
2006-07-28  1:29           ` ricknu-0
2006-07-28  1:56             ` Nicholas Miell
2006-07-28 12:50           ` Alan Cox
2006-07-28 20:24             ` Lars Noschinski
2006-07-28 21:31               ` Nicholas Miell
2006-07-27 19:46 ` [RFC][PATCH] A generic boolean (version 7) ricknu-0

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=44C02F35.4000604@garzik.org \
    --to=jeff@garzik.org \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=getshorty_@hotmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pwil3058@bigpond.net.au \
    --cc=ricknu-0@student.ltu.se \
    --cc=vlobanov@speakeasy.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