Re: Graphic converter query - transparency

"Andrew Stephenson" <ames@[EMAIL PROTECTED]
> wrote in message 
news:1215348043snz@[EMAIL PROTECTED]
> In article <1ijnk3v.ajmuwp7ix6beN%peterd.news@[EMAIL PROTECTED]
>
>    peterd.news@[EMAIL PROTECTED]
 "Pd" writes:
>
>> Andrew Stephenson <ames@[EMAIL PROTECTED]
> wrote:
>>
>> > In article <1ijmnx1.iya47k1bw8dmoN%peterd.news@[EMAIL PROTECTED]
>
>> >      peterd.news@[EMAIL PROTECTED]
 "Pd" writes:
>> >
>> > > Jim <jim@[EMAIL PROTECTED]
> wrote:
>> > >
>> > > > REPEAT
>> > > >       JIM: IT IS
>> > > >       ROWLAND: IT ISN'T
>> > > > UNTIL (HEAT_DEATH_OF_UNIVERSE == TRUE)
>> > >
>> > > Added to Macros. Ta.
>> >
>> > For increased cross-platform ****tability, try encoding in "C":
>> >
>> > void Argybargy(int Topic)
>> > {
>> > int Jim, Rowland;
>> >
>> > srand(Topic);
>> > Rowland = rand();
>> > for (;;)
>> > Rowland = (Jim = Rowland ^ ~0) ~0;
>
> Which should, of course, read:
>    Rowland = (Jim = Rowland ^ ~0) ^ ~0;
>
> We did all spot the boo-boo, didn't we?

Yes, the fact you seemed to have purposefully obfusticated it therefore 
making errors harder to spot, as well as the fact it didn't produce the 
correct output, thus failing in its requirements.
I hope we all learned a lesson here!

>> In a sudden burst of nostalgia, I thought I'd try the same thing
written
>> in Lisp but even more generalised, since anything that happens more
than
>> once on usenet probably appears as a pattern elsewhere. Dragging out my
>> Lisp notes from nearly thirty years ago (yes I still have them,
>> accessible - sad eh?) I remember why my exam results for the Lisp
>> section were so poor.

Sick man!

wouldn't it be just a simple:

(loop
  (print "Jim: it is")
  (print "Rowland: it isn't"))


> LISP is one of those things Heard About (ie: drunken travellers
> encountered in back street bars, raving of horrors; in the heat
> of the night, sinister jungle drums pounding pounding pounding;
> choking cries from within the graveyard; &c) but never actually
> handled (ew-w-w-w...) by me.
>
> Is LISP the one with too many parentheses?

Too many is of course subjective. But for people whos job isn't creating 
keyboards with especially resilliant parentheses keys, probably!

-- 
Woody