Yeah sure blame it on him. (Though it's definitely more than partly true, you love it.) I had a serious question, is it being ignored?
Sorry, but no - I don't like it. I prefer the kind of discussions you can have with zxDunny, Peter (BaCon) or Marcus (NaaLaa), for example. Remind me - were you a member of old
basicprogramming forum? While it's fun to read Aurel's surreal English for some time, it becomes annoying very quickly and destroys every single topic, especially that 80% of his arguments are personal attacks, copy/paste insults and a demonstration of a total lack of knowledge of anything beyond BASIC and WinApi (
"https is just another crap" etc.). But the worst are his lame attempts to be funny and make linguistic jokes.
Sorry, I missed you questions. Here are the answers:
How hard is it to change your output to this? (attached)
Python:
x = [120, 135, 345, 345, 1890, 12, 120, 12, 135, 712, 78, 120]
print(map(lambda a: "Tomaaz " + str(a), sorted(list(set(x)), reverse=True)[0:3]))
NewLisp:
(set 'x '(120 135 345 345 1890 12 120 12 135 712 78 120))
(println (map (fn (x) (append "Tomaaz " (string x))) (slice (sort(unique x) >) 0 3)))
And how do these things handle floats? The forth line? I am curious the decision it would make for 1, 1.0, 1. and .99.... would they be the same or each unique?
In Python and NewLisp 1 and 1.0 are treated as the same number. In Ruby they aren't. 0.99..... in all three languages is unique element, however, while Ruby and Python keep the value, NewLisp is changing it slightly to something like 0.999999
89999 (different number representation).