Re: best of perl6 for tutorial

herbert breunung schrieb: > its understood that i will try, once finished to translate it for the > pugs trunk. Might have been better vice versa. First write it in english and then translate it to german. This way you would've got more responses on that... -Thomas

Re: S04 - forbidden coding-style

> Bearing that in mind, would the eye-socket-burning > > return $foo > IF $something; > > really be so bad? Operators/reserved words should be lowercase. Period. ;) I think that this would heavily break consistency, annoying new users. -Thomas

Re: S04 - forbidden coding-style

Markus Laire schrieb: >> Operators/reserved words should be lowercase. Period. ;) >> I think that this would heavily break consistency, annoying new users. > > There are already many uppercase reserved words in perl6: > > Pseudo-packages from S02 > MY, OUR, GLOBAL, OUTER, CALLER, CONTEXT, SUPER,

Re: renaming "grep" to "where"

e meaning, what's not always the case when you're reading code (of a language) that you haven't read for a while. Also you can usually type them more quickly as the word-charactes have a more prominent position than the special characters on most keybords. Best Regards -- Thomas

Re: renaming "grep" to "where"

don't think that this qualifies as a compelling > reason to change it - especially since it's so easy to add aliases via > modules As Smylers said above: Please, no more aliases. They only create confusion. Regards -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: Y not

e to create an operator with the same name? zip(@a; @b) -> function @a zip @b -> operator Or would that lead to grammar ambiguities, that are impossible to resolve? -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: Y not

the usability of a tool greatly influences it's acceptance and usage, this is a point, where we really should think about. -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

for ... else

stuff) { .. } } else { .. } many times. An else block would save keystrokes and would make the code more readable. Python also has it. What do you think? -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: for ... else

" } end { say "The end has been reached. 42 not found." } empty { say "No items." } -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: for ... else

ng where I'd say "wow, thats an easy solution to my problem!". It's a bit complicated, because you have to understand and combine several concepts. That's elegant. But not easy, I think. I think it's not simple enough for this simple kind of problem. -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: for ... else

Darren Duncan schrieb: > At 11:17 PM +0100 3/3/07, Thomas Wittek wrote: >> Larry Wall: >>> : if ($item = 'foobar') { >> >> == of course ;) >>> If you actually wrote that, then you'll always find that the first >> > item ha

Re: for ... else

/Any/gather directly, I think. > On the other hand, there is no important reason for it because C< > > for @rray -> $el {} > if ! @rray {} > > should work. It's short and easy to understand. Agree, this looks good indeed. -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: Is Perl 6 too late?

e_of_the_co_6.html [2] http://www.google.com/trends?q=perl%2C+python+-snake%2C+ruby People not only want code that _is_ sexy, but they also want it to _look_ sexy. -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: Is Perl 6 too late?

eryone agreed that sigils (or forced semicolons, or tons of operators, ...) are more bad than good (and this seems like persuading the pope to allow homosexual muslims to marry with priests) the design process is probably too far to introduce such dramatic changes. Sadly. -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: Is Perl 6 too late?

warning for that. So maybe it'd be a good idea to completely drop it. People not only want code that _is_ sexy, but they also want it to _look_ sexy. At least almost everyone to whom I said, that I do most work in Perl, responded with some sentence containing the word "ugly" or &

Re: Is Perl 6 too late?

Andy Armstrong schrieb: On 14 May 2007, at 11:51, Thomas Wittek wrote: I also can't remember that I ever named a variable like a "reserved word" or operator. And even if I could, I'd consider it to be bad style. How did you know which reserved words and operators were goi

Re: Is Perl 6 too late?

f being open for ideas and discussing them from a neutral point of view? -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: Is Perl 6 too late?

Andy Armstrong schrieb: On 14 May 2007, at 12:31, Thomas Wittek wrote: How did C, C#, Java, Ruby, Python, Lua, JavaScript, Visual Basic, etc. know? They didn't. If there is a new release, you always have to check if your code still runs. I think that may be the point I'm maki

Re: Is Perl 6 too late?

tional hint for the type. -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: Is Perl 6 too late?

ason for them. > I agree. You need less ignorant colleagues. I'm not sure Perl 6 can fix > that. I don't think that it's a point of ignorance. Especially as they (and enough other people on the web) only seem to be ignorant regarding Perl. Strange, huh? > By the way, I&

Re: Sigils by example

Juerd Waalboer wrote: > Thomas Wittek skribis 2007-05-14 22:20 (+0200): >> But I think that the name of an identifier (noun/verb, single/plural, >> the meaning of the word) already gives enough context to understand what >> type it is. > > [examples] You are right,

Re: Is Perl 6 too late?

Juerd Waalboer schrieb: > Thomas Wittek skribis 2007-05-14 0:42 (+0200): >> excessive use of special characters (/\W/). > > This seems to be "I don't like regexes". Ignoring for now that Perl 6 > regexes will be more verbose and thus easier to read for someone

Re: explicit line termination with ";": why?

d of the common cases. -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: Is Perl 6 too late?

; I think the lack of value here outweights the "savings" of one character > per line. But even if the advantage of line termination is low (some characters saved, some people might say it looks cleaner), I cannot see any advantage of semicolon termination. -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: Sigils by example

chromatic schrieb: > On Monday 14 May 2007 15:48:24 Thomas Wittek wrote: > >> But it should be no problem to put out a warning/error at runtime (or >> maybe even at compile time) when a variable name clashes with a method >> name. > > Do you always know all of t

Re: Sigils by example

Juerd Waalboer schrieb: > Thomas Wittek skribis 2007-05-15 0:48 (+0200): >>> The Perl Way: >>> $object.foo() calls the method called "foo". >>> $object.$foo() calls the method that is in the variable $foo. >> My way: >> someref = &somemeth

Re: explicit line termination with ";": why?

n explicit marker for "don't stop here, keep going". That's the pro-semicolon reason that makes most sense in all comments that I've read so far in this discussion. But maybe that's just something where you have to get used to. -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: propose renaming Hash to Dict

.. So there is no perfect candidate in the above list. But in my opinion they are still more "english" than "hash". Additionally I believe it would be easier to learn that it's (e.g.) a dictionary that just is not ordered than learning a whole new word li

Re: propose renaming Hash to Dict

ed beef hash". To conclude, as hash definitely tastes better than a dictionary, we should stick to that name. ;) At least nobody can say that Perl is bad taste! -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]

Re: POD <-> Code entanglement

ithout guessing) determine the documentation for a certain element. Also you could automatically test if every method/class/.. has been documented etc. Semantics are very useful in documentation, why throw them away? -- Thomas Wittek http://gedankenkonstrukt.de/ Jabber: [EMAIL PROTECTED]