Re: Perl5 -> Perl 6 Translations Design Document

Sage La Torra writes: > http://infohost.nmt.edu/~slatorra/conversionstageone.txt You say this: -Hash in interprative context: "%hash" -> "%hash{}" (also @{[...]} -> {...}) Hashes don't interpolate in Perl 5, so that's not an issue (unless I'm misunderstanding what you meant). But using "{.

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

Thomas Wittek wrote: >> Noone other than Mediawiki uses the Mediawiki syntax. I posit >> that the reason is that that syntax blows chunks. > > I have to agree. 'bold and italic' is definitely not what I > understand as an intuitive syntax. Hi everyone, I'd like to mention that the med

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

Ask Bjørn Hansen <[EMAIL PROTECTED]> writes: > Woah, we are getting really far away from talking about perl6 > here... Kind of a usenet law or corollary? "Every discussion about wikis ends in a discussion about the best wiki syntax." Steffen -- Steffen Schwigon <[EMAIL PROTECTED]> Dresden Perl M

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

Udo Güngerich schrieb: > Why not doing a wiki system that does NOT have a fix syntax but rather > allows defining its syntax rules in e.g. YAML and thus being entirely > flexible? > [..] > It should have a proper user/groups system as well... > [..] > Why not give the wiki a web service API [..] G

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

> Ask Bj�rn Hansen <[EMAIL PROTECTED]> writes: > > Woah, we are getting really far away from talking about perl6 > > here... > > Kind of a usenet law or corollary? "Every discussion about wikis ends You're being a bit optimistic there, aren't you? The only way you'd end a my-wiki-is-better-than-y

Re: namespace bug 2?

Am Dienstag, 18. April 2006 18:19 schrieb Chip Salzenberg: > > On a side note, is there a way to get at the parent namespace if you have > > a namespace? I don't see anything in the PDD about it. (Seems you can > > only walk *down* the hierarchy, not up.) > > That's true.  Given aliasing there may

[perl #39313] [TODO] or [BUG] improve PMC compiler

# New Ticket Created by Leopold Toetsch # Please include the string: [perl #39313] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=39313 > It's easy to add 'invalide' code to .pmc files. E.g. I had defined: METHOD pare

~~ with *

I only vaguely recall the discussions a while back about what smart-matching against Booleans should do. IIRC, there are two positions, and a good argument for either side: C<$foo ~~ True> means C; C<$foo ~~ False> means C or C<$foo ~~ True> means C; C<$foo ~~ False> means C The first of these ad

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

Iraq invasion indeed wait, shouldn't go there. I particularly like the syntax of Textile or even Markdown (preferring the former). In Ruby-land, these exist as RedCloth and BlueCloth. I understand porting isn't fun, but I think that this is a viable option, if not a great choice. Not that th

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

On Tue, 2006-06-06 at 10:59 -0400, Matt Todd wrote: > I particularly like the syntax of Textile or even Markdown (preferring > the former). In Ruby-land, these exist as RedCloth and BlueCloth. I > understand porting isn't fun, but I think that this is a viable > option, if not a great choice. Fo

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

* Markdown does not have tables. * Textile does not have paragraphs in table cells. * Kwiki does not have paragraphs in table cells. Unless someone comes up with another way to do side-by-side layouts (extremely useful for showcasing differences between Perl 5 and Perl 6), all of these formats ar

statement-ending } with if

Can someone explain to me how } on a line on its own can end a statement (as described in the second section of S04), but the following still works? if $condition { ... } else { ... } i.e. Why doesn't the } on the fourth line terminate the if statement, leaving the compiler terminally confuse

OT: "my wiki syntax is better than yours" (was: $1,000 prize for Perl 6 Wiki written in Perl 6)

* Juerd <[EMAIL PROTECTED]> [2006-06-06 17:50]: > side-by-side layouts (extremely useful for showcasing > differences between Perl 5 and Perl 6) Good point. > * Markdown does not have tables. But it lets you embed verbatim HTML as an escape hatch for constructs that it does not model, and althou

Re: namespace bug 2?

On Tue, Jun 06, 2006 at 04:32:27PM +0200, Leopold Toetsch wrote: > Am Dienstag, 18. April 2006 18:19 schrieb Chip Salzenberg: > > > On a side note, is there a way to get at the parent namespace if you have > > > a namespace? I don't see anything in the PDD about it. (Seems you can > > > only walk *

Re: namespace bug 2?

On Jun 6, 2006, at 20:11, Chip Salzenberg wrote: NameSpace.parent() is now implemented. Cool. I'm afraid it needs to be set_parent() and get_parent(), It is now get_parent(). leo

Re: OT: "my wiki syntax is better than yours" (was: $1,000 prize for Perl 6 Wiki written in Perl 6)

There are alternatives to using tables for side-by-side using paragraphs. Simply having one cell for each line, for instance, allows for highlighting green the added lines and red the removed ones, etc. Also realize that it is not necessarily the duty of Textile (et al) to handle that aspect beyo

Re: OT: "my wiki syntax is better than yours" (was: $1,000 prize for Perl 6 Wiki written in Perl 6)

> Also realize that it is not necessarily the duty of Textile (et al) to > handle that aspect beyond text formatting. A diff or history-revision > view goes beyond the context of the tool. I don't think Juerd was talking about tables for the purposes of showing version diffs, but so you can give p

Re: OT: "my wiki syntax is better than yours" (was: $1,000 prize for Perl 6 Wiki written in Perl 6)

Matt Todd skribis 2006-06-06 16:46 (-0400): > There are alternatives to using tables for side-by-side using > paragraphs. Simply having one cell for each line, for instance, allows > for highlighting green the added lines and red the removed ones, etc. Visually pleasing, but technically incorrect,

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

Quoth [EMAIL PROTECTED] (Juerd): > > * Markdown does not have tables. > * Textile does not have paragraphs in table cells. > * Kwiki does not have paragraphs in table cells. > > Unless someone comes up with another way to do side-by-side layouts > (extremely useful for showcasing differences bet

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

Thomas Wittek wrote: > > Good ideas. But maybe we should start a bit smaller ;) > It might be a good idea to create a list of features separated in > several increments (releases) to get a running system early. Absolutely. > I could imagine increments like "Parsing/Converting", "Storage > backe

OT: "my wiki syntax is better than yours" (was: $1,000 prize for Perl 6 Wiki written in Perl 6)

* Ben Morrow <[EMAIL PROTECTED]> [2006-06-07 01:25]: > Preferably something rst-like? I was wondering why noone had proposed Kwid yet. Doesn’t anyone like it? Regards, -- Aristotle Pagaltzis //

Re: Perl5 -> Perl 6 Translations Design Document

"interpolative context" ment the perl 5 side, where the double quotes should cause interpolation. Maybe not the best phrase to identify it, now that you mention it. Sage On 6/6/06, Aaron Crane <[EMAIL PROTECTED]> wrote: Sage La Torra writes: > http://infohost.nmt.edu/~slatorra/conversionstageo

Inconsistent find_global 'not found' handling

If given a namespace key with a single component, and a name that is not found, e.g. $P2 = find_global ["Foo"], "bazz" Parrot says "Global 'bazz' not found", obeying PARROT_ERRORS_GLOBALS_FLAG (presumably). On the other hand, if the namespace name is compound: $P2 = find_glob

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

I also agree that Object Oriented Design would work wonderfully well here. The key here is prototyping its shape and then filling in the details once it has taken this shape. I like the term 'messages' for methods because it reminds me that the objects must send requests, forms of communication,

Re: OT: "my wiki syntax is better than yours" (was: $1,000 prize for Perl 6 Wiki written in Perl 6)

Juerd, My mistake: I misunderstood what you were saying (probably due to haste). But really, then, there are alternatives to using tables, such as DIVs, as well as simply modifying the parsing step to also parse for this special case in addition to Textile or what-have-you. I guess if I said an