Pascal J Bourguignon 〔p…@informatimago.com〕 wrote:
> Not at all. (Yet some other fodder for Xah's idiocy articles, sorry).
you mean my articles describing idiots like you?
Here's a juicy passage of Pascal J Bourguignon fellow, in which you can get a glimpse of his highness:
«Ruby's been done by some Japanese newbie… I guess there was some language barrier preventing him to learn from the 50 years of occidental experience in programming language design. At least, he wasn't a "linguist"… In any case, why should we suffer for THEIR incompetences?!?»
Xah
On Jun 11, 9:51 pm, "Pascal J. Bourguignon" 〔p…@informatimago.com〕 wrote:
│ Alan Mackenzie 〔a…@muc.de〕 writes:
│ │ Hi, Xah.
│
│ │ Xah Lee 〔xah…@gmail.com〕 wrote:
│ ││ in a elisp program, if i have created a temp var (but not using let)
│ │ ….
│
│ │ As a matter of interest, how do you do that?
│
│ ││ …. and later i want to delete the var, i can do:
│
│ ││ (setq temp1 nil)
│
│ ││ or is it better to do
│
│ ││ (unintern 'temp1)
│
│ │ Shouldn't much matter. Probably better to set it to nil, because that's
│ │ more usual. OTOH, if you want to detect an error should temp1 be
│ │ subsequently accessed, then uninterning it will be better.
│
│ Not at all. (Yet some other fodder for Xah's idiocy articles, sorry).
│
│ (defvar temp1 42)
│
│ (defun f ()
│ temp1)
│
│ (unintern 'temp1)
│
│ (f) --│ 42
│
│ ││ The temp1 var holds a big list, and there are few more, e.g. temp2,
│ ││ temp3.
│
│ │ Either approach will allow these lists to be garbage collected.
2011-06-12
Subscribe to:
Post Comments (Atom)

0 comments:
Post a Comment