:> I really don't like this idea. Adding braces and dummy do/while,
:> but I don't like casting the passed expression to void simply as
:> a means of avoiding a compiler warning.
:
:The cast is needed as the value of the element should explicitly be
:ignored for the default macro.
:
:
On Wed, Feb 18, 2009 at 11:36:41AM -0800, Matthew Dillon wrote:
>
> :
> :On Wed, Feb 18, 2009 at 10:49:29PM +1100, Dmitri Nikulin wrote:
> :> #define RB_AUGMENT(x) ((void)x)
> :
> :Replace that with
> :#define RB_AUGMENT(x) do { (void)x; } while (0)
> :
> :Joerg
>
> I really don't like this
:
:On Wed, Feb 18, 2009 at 10:49:29PM +1100, Dmitri Nikulin wrote:
:> #define RB_AUGMENT(x) ((void)x)
:
:Replace that with
:#define RB_AUGMENT(x) do { (void)x; } while (0)
:
:Joerg
I really don't like this idea. Adding braces and dummy do/while,
but I don't like casting the passed expre
Colin Adams wrote:
-- Forwarded message --
From: Colin Adams
Date: 2009/2/18
Subject: Re: EUREKA - was the 'why' of pseudofs
2009/2/18 Bill Hacker :
Proven pattern among Odontata, too:
http://ecoevo.uvigo.es/Olalla/index_en.htm
That should be Odonata (= tooth-jawed) (Dragon
-- Forwarded message --
From: Colin Adams
Date: 2009/2/18
Subject: Re: EUREKA - was the 'why' of pseudofs
To: Bill Hacker
2009/2/18 Bill Hacker :
> Proven pattern among Odontata, too:
>
> http://ecoevo.uvigo.es/Olalla/index_en.htm
That should be Odonata (= tooth-jawed) (Dragonf
Matthew Dillon wrote:
There are several reasons for using PFSs.
EUREKA!
Matt - you've re-invented Ramphotyphlops braminus:
Weigh this:
PFS = Parthenogenetic File System
hammer pfs-master = select a host.
hammer pfs-slave = induce ovulation.
hammer mirror-copy = self-inseminate th
On Wed, Feb 18, 2009 at 10:49:29PM +1100, Dmitri Nikulin wrote:
> #define RB_AUGMENT(x) ((void)x)
Replace that with
#define RB_AUGMENT(x) do { (void)x; } while (0)
Joerg
Steve O'Hara-Smith wrote:
On Wed, 18 Feb 2009 11:10:01 +0100
Jost Tobias Springenberg wrote:
If you want to have seperate partitions instead of PFS, thats perfectly
fine, nobody forces you to use PFS everywhere. In fact It might be very
reasonable to keep data from home directories seperated f
On Wed, 18 Feb 2009 11:10:01 +0100
Jost Tobias Springenberg wrote:
> If you want to have seperate partitions instead of PFS, thats perfectly
> fine, nobody forces you to use PFS everywhere. In fact It might be very
> reasonable to keep data from home directories seperated from other data
> or the
Hi all,
I've been using tree.h (
http://www.dragonflybsd.org/cvsweb/src/sys/sys/tree.h ) in C projects
for a long time, and it has bothered me to have "suggest braces around
empty body in if-statement" warnings from GCC. Old GCCs didn't even
have a -Wno-empty-body flag, and I think the GCC in Drag
Jost Tobias Springenberg wrote:
I do not want to sound offensive here but I don't get the point of this
discussion at all.
What exactly is wrong with null mounts and / or the way PFS work ?
If you want to have seperate partitions instead of PFS, thats perfectly fine, nobody
forces you to use P
I do not want to sound offensive here but I don't get the point of this
discussion at all.
What exactly is wrong with null mounts and / or the way PFS work ?
If you want to have seperate partitions instead of PFS, thats perfectly fine,
nobody
forces you to use PFS everywhere. In fact It might b
Matthew Dillon wrote:
There are several reasons for using PFSs.
* Shared allocation space. You don't have to worry about blowing
out small filesystems and having to resize them.
* Each PFS has its own inode space, allowing mirroring to be used
to manage backups on a per
13 matches
Mail list logo
