I'm a German monk and I seem to remember I heard his name before, but didn't recognize him when I commented.

This guy seems to be very sarcastic and provocative, he also admits posting wrong stories in his blog to test the "media competence" of his audience.

While I admit such personalities are useful in niches like open source and IT security, I'm not sure I want to meet them in real life¹.

Anyway his comment was only limited to three phrases:

Der Perl-Talk war großartig. Wer den verpasst hat, und mit Perl zu tun hat, sollte sich den dringend angucken. Popcorn bereithalten! :-)

The Perl-talk was great. Those who missed it and have to deal with Perl, should urgently watch it. Keep your popcorn ready! :-)

I haven't seen the video yet, but I have to admit that meditating about fat comma was worth talking about it.

• I'm not sure which backwards compatibility would break if => would force scalar context on the RHS. Till now I can only imagine cases of syntactic sugar broken.

  After all that's the behavior most people seem to expect, list flattening like @c=(@a,@b) can still be done with a simple comma.

• Furthermore I'm not sure why HTTP responses aren't easily sanitized, such that fields which are not expected to hold multiple values are blocked/filtered before any further processing takes place.

  For instance: Why should I even handle requests with multiple real_name ?

Also worth noting that Sheldon (aka Python) has DWIM mechnanisms, when returning multiple values.

>>> def func(): return 1
... 
>>> func()
1
>>> def func(): return 1,2
... 
>>> func()
(1, 2)
>>> def func(): return (1)
... 
>>> func()
1
>>> def func(): return (1,)
... 
>>> func()
(1,)
[download]

As you can see one element is "scalar", more are tuples and it's not that intuitive how to return a one element tuple.

¹) For instance: I have friends who organized conferences with Richard Stallman and never want to meet him in real life again. This doesn't diminish his importance.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.