Re: Proposal: B_ARRIER (addresses wapbl performance?)

[der Mouse <mouse%Rodents-Montreal.ORG@localhost>]

>>>> B_ARRIER
>>> I'd suggest B_BARRIER.
>> [...], I also think B_BARRIER is better due to consistency with the
>> other flag names.
> Tell that to the people who named the "iberty" library (called with
> -liberty on the linker command line) or the "rarian" package which
> contains a library "librarian".

I've never liked libiberty's name, and that is a substantial part of
the reason.  I wasn't aware of rarian before I saw your note, but I
feel rather the same way about it too.

I've seen C code that does

#ifdef EBUG
...debugging code...
#endif

for similar reasons (designed to be compiled with -DEBUG).  Mercifully,
I haven't seen very much such code. :-/

There are good places for clever and amusing names.  I do not think any
of the examples above are such places, and I do not think the existence
of bad examples is a reason to create more bad examples.  (Cartoon:
people seated around a table playing a board game.  Caption reads
"Colonel Panic...in the shared library...with the named pipe."  _That_
is a good place for clever and amusing names.  xkcd #327 is another.)

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B