• That's not a peace sign, that's an upside-down mercedes bens sign.
• All of your "obfuscations" all do the same thing - get numbers and convert them to text using chr. It has been done and it is getting really old.

s&&q+\+blah+&oe&&s<hlab>}map{s}&&q+}}+;;s;\+;;g;y;ahlb;veaD;&&print;
[download]

• That is actually a peace sign
• It's just my third 'obfuscation', so please, try to be a little bit more friendly, or, at least, not to just criticize what other people do...


Asmo

UPDATE :Ok, thx damian for your support ;)

Dude, it really is an upside-down Mercedes Benz emblem. Check this out if you're still unsure...

The sentiment is sound, though, Asmo. ++ for the effort...

higle

• I agree with your first (despite your horrendous spelling of "Benz")
• Give Asmo a break. OK, so s/he likes chr. Someone piss in your cereal this morning?
This ain't the first time you jumped on some newbie. You ever think it's your attitude that's getting really old, you little weasel?

Side note: There have been a number of variations of the so-called 'peace sign', and at least one of them looked like the one in this thread, either because it was yippie-influenced or because it corresponded to the 2-finger peace 'gesture', or maybe both.

well, when i saw damian's reply, i though 'huh, he might be right' then i searched a little bit, and, they are actually, different version of 'the' peace sign...

Thx for your reply.

Asmo

%make war
Make: Don't know how to make war. Stop.
[download]

-- stefp

I think the issue was how many branches there are (i.e. the peace sign that I know of has four spokes coming out from the center, whereas this obfu and mercedes logo only have three.

-Blake

for(@h1){$_=chr;print}

get to know the $_ special variable. it'll save you tons of typing and redundant statements. also, the for and foreach loops are interchangable. Any place you can use one you can use the other. example:
foreach ($i=0;$i < 10;$i++){do something}
for is three characters foreach is seven, guess which one most Perl programmers use :)
hint: think lazy

Perhaps the choice of using the code the programmer did is based on the aesthetic layout?

While you are at it? Why bother reassigning the result of chr to $_? Just drop that line alltogether to get  for(@h1){ print chr; } and of course if your decision is to be based on the number of characters you can go to print chr for(@h1); but getting the smallest WTDI is golf and not obfuscation.

I'd personally use:
print map chr, @h1;
But to each their own. I was just offering some advice.