Re: Coercing a list to string (nasty behaviour IMHO)
Re: Coercing a list to string (nasty behaviour IMHO)
- Subject: Re: Coercing a list to string (nasty behaviour IMHO)
- From: Brennan <email@hidden>
- Date: Wed, 29 Aug 2001 10:37:03 +0200
Nigel Garvey wrote
>
Or to put it another way: If you write "MY TROUSERS" on a piece of slate,
>
put the slate on a piece of paper, and write to the left of it "Set fire
>
to ", your assistant will come in in the morning, read the instruction
>
"Set fire to MY TROUSERS", and coerce the garment to ash. If instead you
>
put the slate in a box - along with yesterday's Daily Telegraph a
>
three-toed sloth - and leave the message "Set fire to this box", the
>
slate will not turn to ash and neither will your trousers.
Very nice post!
Thanks for gathering all these nits into a single post. I drive myself crazy with exactly these issues, and the non-optional use of 'get' was new to me.
I will archive that for future reference. (No pun intended).
-Brennan