[svn:perl6-synopsis] r12284 - doc/trunk/design/syn

Author: larry Date: Wed Sep 20 22:07:47 2006 New Revision: 12284 Modified: doc/trunk/design/syn/S02.pod doc/trunk/design/syn/S03.pod doc/trunk/design/syn/S06.pod doc/trunk/design/syn/S12.pod Log: The | sigil and operator. Modified: doc/trunk/design/syn/S02.pod ==

Re: Capture sigil

Larry Wall wrote: Okay, I think this is worth bringing up to the top level. Fact: Captures seem to be turning into a first-class data structure that can represent: argument lists match results XML nodes anything that requires all of $, @, and % bits. Fact: We're currently going

Re: Capture sigil

Larry Wall wrote: On Wed, Sep 20, 2006 at 05:18:12PM -0400, Aaron Sherman wrote: : For this reason, I'd suggest putting away the Latin-1 glyphset and : instead focusing on developing operators to act on containers with : multiple access methods and their expanded forms. There's already goi

Re: renaming "grep" to "where"

On Wed, Sep 20, 2006 at 11:44:49PM -0400, John Macdonald wrote: : On Wed, Sep 20, 2006 at 07:11:42PM +0100, Andy Armstrong wrote: : > On 20 Sep 2006, at 19:05, Larry Wall wrote: : > >Let it be. :) : > : > I could just as easily have called for a revolution :) : : No, you should have quoted diffe

Re: renaming "grep" to "where"

On Wed, Sep 20, 2006 at 07:11:42PM +0100, Andy Armstrong wrote: > On 20 Sep 2006, at 19:05, Larry Wall wrote: > >Let it be. :) > > I could just as easily have called for a revolution :) No, you should have quoted differently: > On 20 Sep 2006, at 19:05, Larry Wall whispered words of wisdom: > >

Re: the CGI.pm in Perl 6

On Thu, Sep 21, 2006 at 12:43:41AM +0200, Juerd wrote: : > my @bar = @{ $q->param->{ 'bar' } }; : : my @bar = $q.param.'@'; : my @bar = @ $q.param; That should work but my preference is just my @bar = $q.param[]; That is, empty .[] has the same arrayifying semantics as @. (This is curr

Re: Web development I: Web::Toolkit

On 9/20/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote: I did qualify my statement. I'm sorry, I must have missed it. :-) Aankhen

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

On 9/20/06, Fagyal Csongor <[EMAIL PROTECTED]> wrote: And maybe expand Web::HTML something like: Web::Markup::HTML Web::Markup::XHTML Web::Markup::WML etc... But that's might as well be too much. If those are modules to generate markup, I don't see why they should under the Web namespace. Ther

Re: Capture sigil

On Thu, Sep 21, 2006 at 12:45:46AM +0100, Smylers wrote: : Larry Wall writes: : : > Conjecture: We need a corresponding sigil to request captureness. As : > Bikeshed: What should that sigil be? : : What's * doing these days? Thought a lot about that one, but I think it's more useful in 0..* and

Re: Web development I: Web::Toolkit

* Aankhen <[EMAIL PROTECTED]> [2006-09-21 03:15]: > On 9/19/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote: > >On top of this, roughly 80% (or so it sometimes feels) of the > >useful attributes defined in HTML do not have any tangible > >bro

Re: Web development I: Web::Toolkit

On 9/19/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote: * Aankhen <[EMAIL PROTECTED]> [2006-09-17 21:00]: > XHTML 1.0 and 1.1 offer no practical benefits over HTML, but > tangible disadvantages. To be fair, XHTML does let you embed MathML and SVG (as well as XForms, pending browser support) in your

Re: Perl6 "style-guide"

* Juerd <[EMAIL PROTECTED]> [2006-09-21 00:50]: > I've been thinking in Perl 6 terms for quite a while now, I won’t dismiss this claim, but the [EMAIL PROTECTED] = qw( Exporter );` example I mentioned in the other mail cautions me from believing that anyone is particularly fluent with Perl 6 quite

Re: Capture sigil

Larry Wall writes: > Conjecture: We need a corresponding sigil to request captureness. As > Bikeshed: What should that sigil be? What's * doing these days? Smylers

Re: the CGI.pm in Perl 6

* Juerd <[EMAIL PROTECTED]> [2006-09-21 00:45]: > And I wouldn't want the nullbyte mistake again. Let's just > stick to the last given value instead. Nobrainer. The nullbyte thing was a Perl-4-ism. > Also, I want parameters to be able to do a certain Upload role, > which adds terribly useful meth

Re: Capture sigil

On Wed, Sep 20, 2006 at 05:18:12PM -0400, Aaron Sherman wrote: : Consider this the first test of the first-classness of objects in Perl : 6. You have an object that's something not entirely unlike: : : class Capture { has $.scalar; has @.array; hash %.hash } : : I think the addition of a sigi

Re: Perl6 "style-guide"

On Wed, Sep 20, 2006 at 04:16:32PM -0700, Darren Duncan wrote: : And in fact, I expect that PBP was written to be forward compatible : to Perl 6, as it could describe styles that should be natural in Perl : 6, even if less so in Perl 5. Indeed, I know for a fact that it was. (Though the treatme

Re: Perl6 "style-guide"

At 4:56 PM +0200 9/20/06, Fagyal Csongor wrote: I was wondering if there is (or there should be) a documentation on how to elegantly write Perl6 code. I have found that Damian's "Perl Best Practices" still works very well for Perl 6 code, so I still apply that where reasonably possible. And

Re: Perl6 "style-guide"

A. Pagaltzis skribis 2006-09-20 22:29 (+0200): > * Fagyal Csongor <[EMAIL PROTECTED]> [2006-09-20 17:00]: > > I am afraid that when I will be starting to write Perl6 code, > > it will be too much Perl5-ish, > Even with a style guide, your Perl 6 code will still be > Perl-5-ish. And even once it???s

Re: the CGI.pm in Perl 6

A. Pagaltzis skribis 2006-09-20 22:39 (+0200): > * Juerd <[EMAIL PROTECTED]> [2006-09-20 22:25]: > > I think it's time we moved away from the param method, and > > started using a hash. > I don???t know about that. The `param` method has the nice property > that it allows you to pretend everything?

Re: Capture sigil

On Wed, Sep 20, 2006 at 12:28:10PM -0700, Larry Wall wrote: > Bikeshed: What should that sigil be? And if it's in Latin-1, what's the > ASCII workaround? The one that springs out to me is: > ¤ 00A4CURRENCY SIGN Probably because it looks like a container with something cap

[perl #40379] [TODO] investigate use of tools/dev/as2c.pl

The plan behind of as2c.pl is and was to create compiler independant machine code for an architecture. masm, gas, nasm, whatever syntax doesn't fit all compilers. Therefore as2c.pl translates gas syntax to a bytestring, which is then used as the asm code. as2c's usage is indeed scarce: when the cod

Re: Perl6 "style-guide"

Aristotle (>): That said, a cheatsheet with broad tips for arrivals from Perl 5 could already be written and will age well. Oh, have a look at docs/other/porting_howto in the pugs svn tree. If nothing else, it's a good starting point.

Re: Capture sigil

On 9/20/06, Larry Wall <[EMAIL PROTECTED]> wrote: Conjecture: We need a corresponding sigil to request captureness. As with @ and %, you can store a capture in a $ to hide it, but we don't have the ability to have capture variables that know how to behave like captures without fakey syntactic hel

Re: Capture sigil

Larry Wall wrote: Okay, I think this is worth bringing up to the top level. Fact: Captures seem to be turning into a first-class data structure that can represent: argument lists match results XML nodes anything that requires all of $, @, and % bits. This is quite true, and wo

OT: Re: Web development I: Web::Toolkit

A. Pagaltzis schrieb: > On top of this, roughly 80% (or so it sometimes feels) > of the useful attributes defined in HTML do not have any tangible > browser support (such as `cite` on `blockquote`/`q`, or > `datetime` on `ins`/`del`). At least without CSS. You can use those tags to create a more s

Re: the CGI.pm in Perl 6

* Juerd <[EMAIL PROTECTED]> [2006-09-20 22:25]: > I think it's time we moved away from the param method, and > started using a hash. I don’t know about that. The `param` method has the nice property that it allows you to pretend everything’s a single value or to use multi-valued params, at your ow

Re: Perl6 "style-guide"

* Fagyal Csongor <[EMAIL PROTECTED]> [2006-09-20 17:00]: > I am afraid that when I will be starting to write Perl6 code, > it will be too much Perl5-ish, Even with a style guide, your Perl 6 code will still be Perl-5-ish. And even once it’s not anymore, six months later you will discover that it’s

Re: the CGI.pm in Perl 6

A. Pagaltzis skribis 2006-09-20 22:01 (+0200): > With roles in P6, you can even make this even simpler. You could > make the HTML generator a role which can be composed onto any > object that `does ParamQuery`. I think it's time we moved away from the param method, and started using a hash. In fac

Re: [PATCH] as2c.pl C-file coda fix

On 9/20/06, chromatic <[EMAIL PROTECTED]> wrote: On Wednesday 20 September 2006 09:53, Jerry Gay via RT wrote: > thanks, applied as r14673, with a minor fix: > > -$print_coda(); > +&print_coda(); I wouldn't mind seeing the '&' go away entirely. It's syntactic noise in this case. you're right,

Re: [PATCH] as2c.pl C-file coda fix

On Wednesday 20 September 2006 09:53, Jerry Gay via RT wrote: > thanks, applied as r14673, with a minor fix: > > -$print_coda(); > +&print_coda(); I wouldn't mind seeing the '&' go away entirely. It's syntactic noise in this case. -- c

Re: the CGI.pm in Perl 6

* Randal L. Schwartz [2006-09-20 19:30]: > To get this to work right, whatever I use for HTML generation > needs to know how to get incoming params. Admittedly, the > interface is simple, but it would have to know if I'm using a > functional form with a hidden object (use CGI qw/param/) Which is

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

* Randal L. Schwartz [2006-09-20 19:30]: > "Fagyal" == Fagyal Csongor <[EMAIL PROTECTED]> writes: >> yet I never needed those HTML generating methods. > > You've never made a sticky form then. False dilemma. You can create sticky forms conveniently without using CGI.pm’s HTML generation stuff. Y

Re: Capture sigil

Oops, I hate typos that result in my writing exactly the opposite of what I meant: In a message dated Wed, 20 Sep 2006, Trey Harris writes: In a message dated Wed, 20 Sep 2006, Larry Wall writes: The obvious ASCII for ¢ would be c/ or C/ or c| or c| or maybe just |. I like ¢,but: c/$foo

Re: Capture sigil

In a message dated Wed, 20 Sep 2006, Larry Wall writes: The obvious ASCII for ¢ would be c/ or C/ or c| or c| or maybe just |. I like ¢,but: c/$foo # ASCII of ¢$foo d/$foo # d() divided by $foo is rather confusing. (Same goes for |). So the Term Term exclusion makes me rather lean tow

Capture sigil

Okay, I think this is worth bringing up to the top level. Fact: Captures seem to be turning into a first-class data structure that can represent: argument lists match results XML nodes anything that requires all of $, @, and % bits. Fact: We're currently going through contortions

Re: renaming "grep" to "where"

> names they're given. "The Beatles" probably sounded like a really > dumb name for a band once. But maybe less dumb than 'The Quarrymen', which was the original name of the band. (They all went to Quarry Bank school, now Calderstones.) Perhaps the renaming, unfettered by their history or by a

Re: call, call(), .call, and captures

Larry Wall wrote: On Wed, Sep 20, 2006 at 11:18:09AM -0400, Aaron Sherman wrote: : Trey Harris wrote: : >Might I propose the following normalization: : > : >1. .call, method definition call(), and .wrap call all take captures. : : >2. .call() and both types of call() all pass on the arguments of

Re: Trying to make a new operator

Richard Hainsworth <[EMAIL PROTECTED]> writes: > Thanks for help. For anyone else, the following works. > > sub infix: {...}; > > (32 grew_by_to 48).say; > > sub infix: ($left, $right) { > return ($right/$left - 1) * 100 ~ '%'; > }; Thanks for reporting the solution back. And it even works wi

Re: renaming "grep" to "where"

On 20 Sep 2006, at 19:05, Larry Wall wrote: Let it be. :) I could just as easily have called for a revolution :) -- Andy Armstrong, hexten.net

Re: renaming "grep" to "where"

On Wed, Sep 20, 2006 at 06:54:11PM +0100, Andy Armstrong wrote: : The Beatles" probably sounded like a really dumb name for a band once. : : Is there a serious objection to letting it be? Let it be. :) Larry

Re: call, call(), .call, and captures

On Wed, Sep 20, 2006 at 11:18:09AM -0400, Aaron Sherman wrote: : Trey Harris wrote: : >Might I propose the following normalization: : > : >1. .call, method definition call(), and .wrap call all take captures. : : >2. .call() and both types of call() all pass on the arguments of the : > current s

[perl #40380] [PATCH] errors on 'make install' - src/pdb.c

# New Ticket Created by "Herbert Poul" # Please include the string: [perl #40380] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=40380 > hi, 'make install' failed due to a change in compilers/imcc/parser.h (rev. 14633) whi

Re: renaming "grep" to "where"

On 20 Sep 2006, at 18:41, Doug McNutt wrote: I never thought about the potential for serious ambiguity in interpretation. The UNIX grep tool is really dissimilar considering that it uses a different regular expression syntax. (perl grep doesn't have to be used with an RE of course) I guess

[perl #40374] [PATCH] C coda fix in parrot/include

thanks, applied as r14676. ~jerry

Re: the CGI.pm in Perl 6

> "Steve" == Steve Pitchford <[EMAIL PROTECTED]> writes: Steve> To be honest I'm not sure I follow your argument. Why does populating a form Steve> from incoming form data require "closer integration" Steve> than, say, pulling it out of a database and populating a form for further Steve> edit

Re: renaming "grep" to "where"

Just a perl 5 physicist here. I had to run to the Camel book to find out that grep existed in the world of perl. But I have done this (from memory): $stuff_in_lines = `grep suntide *.txt`; I never thought about the potential for serious ambiguity in interpretation. The UNIX grep tool is really

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

> "Fagyal" == Fagyal Csongor <[EMAIL PROTECTED]> writes: Fagyal> As a side note I also have to add that I really dislike the Fagyal> "html-functions" CGI.pm currently has. Creating the representation is Fagyal> the task of the designer, not the programmer. It's almost like "echo" Fagyal> in PH

[perl #40373] [PATCH] C coda fix in parrot/config/gen

thanks, applied as r14675. nice work, paul. ~jerry

Re: renaming "grep" to "where"

Quoth [EMAIL PROTECTED]: > On Tue, Sep 19, 2006 at 04:38:38PM +0200, Thomas Wittek wrote: > > Jonathan Lang schrieb: > > > IMHO, syntax should be left alone until a compelling reason to change > > > it is found. While I think it would be nice to have a more intuitive > > > name for grep > > What

[perl #40372] [PATCH] C coda fix in parrot/compilers

thanks, applied as r14674. ~jerry

[perl #40379] [TODO] investigate use of tools/dev/as2c.pl

# New Ticket Created by Jerry Gay # Please include the string: [perl #40379] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=40379 > i'm not sure tools/dev/as2c.pl is used, as the only makefile that calls it isn't generated

[perl #40371] [PATCH] as2c.pl C-file coda fix

thanks, applied as r14673, with a minor fix: -$print_coda(); +&print_coda(); i'm not sure tools/dev/as2c.pl is used, as the only makefile that calls it isn't generated (config/gen/cpu/i386/Makefile), it's not platform-independent, and the files it generates are committed to the repository. but, t

Re: Perl6 "style-guide"

On 9/20/06, jerry gay <[EMAIL PROTECTED]> wrote: don't "just leave this to the community." take part! take advantage of the perl 6 wiki (http://rakudo.org/perl6/index.cgi) and create a page describing the task. write some code yourself. ask folks to contribute, and fix the existing code or add t

[perl #40370] [PATCH] code_coda.t update

thanks, applied as r14671. ~jerry

Re: Perl6 "style-guide"

On 9/20/06, Fagyal Csongor <[EMAIL PROTECTED]> wrote: I was wondering if there is (or there should be) a documentation on how to elegantly write Perl6 code. yes, there should be. I am afraid that when I will be starting to write Perl6 code, it will be too much Perl5-ish, and I will end up rew

Re: call, call(), .call, and captures

Trey Harris wrote: Might I propose the following normalization: 1. .call, method definition call(), and .wrap call all take captures. 2. .call() and both types of call() all pass on the arguments of the current subroutine. > 3. To call with no arguments, use .call(\()) and call(\()). I

[perl #40377] [PATCH] C coda fix in parrot/examples

# New Ticket Created by "Paul Cochrane" # Please include the string: [perl #40377] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=40377 > Hi, This patch adds the C emacs/vim coda to the C-language files under parrot/exampl

Perl6 "style-guide"

Hi, I was wondering if there is (or there should be) a documentation on how to elegantly write Perl6 code. I am afraid that when I will be starting to write Perl6 code, it will be too much Perl5-ish, and I will end up rewriting my code in every 3 months because I hate when my code is not el

[perl #40375] [PATCH] C coda fix in parrot/config/gen

# New Ticket Created by "Paul Cochrane" # Please include the string: [perl #40375] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=40375 > Hi, It seems I forgot to attach the patch to this email. Many apologies! Here it i

[perl #40374] [PATCH] C coda fix in parrot/include

# New Ticket Created by "Paul Cochrane" # Please include the string: [perl #40374] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=40374 > Hi, This patches all C-language files in parrot/include that require the C emacs/vim

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

Juerd wrote: [...] Fagyal Csongor skribis 2006-09-20 15:43 (+0200): Inefficient was probably a bad choice of word. I would rather say: I would not like to see Perl6's CGI.pm as a monster module, which has one part everyone uses, and one hundred other parts that some uses, because I feel t

Re: renaming "grep" to "where"

[EMAIL PROTECTED] wrote: I still don't think we have a consensus that grep needs to be renamed, much less what it should be renamed to. To me, "keep" implies throwing the rest away,I.e., modifying the list. "Select" has the advantage of lacking that connotation. To avoid dissonance with the two

Re: Trying to make a new operator

Thanks for help. For anyone else, the following works. sub infix: {...}; (32 grew_by_to 48).say; sub infix: ($left, $right) { return ($right/$left - 1) * 100 ~ '%'; }; Yuval Kogman wrote: On Sun, Sep 17, 2006 at 16:35:39 +0100, Daniel Hulme wrote: What am I doing wrong? Sounds

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

Jacinta Richardson skribis 2006-09-21 0:13 (+1000): > My biggest gripe with CGI's html methods is the inconsistency in their > names. I use them every now and then, but I always have to go and look > up the documentation. It's "textfield" isn't it? So that would make > this one "passwordfield":

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

Fagyal Csongor skribis 2006-09-20 15:43 (+0200): > Inefficient was probably a bad choice of word. > I would rather say: I would not like to see Perl6's CGI.pm as a monster > module, which has one part everyone uses, and one hundred other parts > that some uses, because I feel those parts should b

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

Fagyal Csongor wrote: > # imagine something like: > $cgi = new CGI; > $html = HTML::CGI->new($cgi); > $html->popup_menu( ... ); # I won't do this, but others might... :) My biggest gripe with CGI's html methods is the inconsistency in their names. I use them every now and then, but I always h

Re: [perl #40364] [PATCH] line endings of perl .t test files

On 9/19/06, via RT Paul Cochrane <[EMAIL PROTECTED]> wrote: # http://rt.perl.org/rt3/Ticket/Display.html?id=40364 > This patch changes the line endings of the files listed below from dos to unix. thanks, applied by bernhard, r14667. ~jerry

Re: [perl #40360] [PATCH] implement loadlib(NULL)

Am Dienstag, 19. September 2006 11:51 schrieb Dmitry Karasik: > > dlopen(NULL,...) on linux returns NULL, and consequently dlsym(NULL,...) > can be used to access shared objects of the main executable. However, on > freebsd dlsym(NULL,...) server somewhat different purpose, and to access > the main

[perl #40371] [PATCH] as2c.pl C-file coda fix

# New Ticket Created by "Paul Cochrane" # Please include the string: [perl #40371] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=40371 > Hi, Attached is a patch for tools/dev/as2c.pl which adds a new subroutine print_coda

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

Erm... Sorry for the bandwith usage again, but what about something like class CGI is CGI::Base does CGI::ParamParser does CGI::HTML { ... } ? To make CGI.pm kind of backward compatible, but separates the layers. (Please excuse my bad syntax/semantics.) - Fagzal

[perl #40372] [PATCH] C coda fix in parrot/compilers

# New Ticket Created by "Paul Cochrane" # Please include the string: [perl #40372] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=40372 > Hi, This is a patch of all .c and .h files found by t/codingstd/code_coda.t that res

[perl #40373] [PATCH] C coda fix in parrot/config/gen

# New Ticket Created by "Paul Cochrane" # Please include the string: [perl #40373] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=40373 > Hi, This patch adds the C-specific emacs/vim coda to all C-language files under parr

Re: renaming "grep" to "where"

I still don't think we have a consensus that grep needs to be renamed, much less what it should be renamed to. To me, "keep" implies throwing the rest away,I.e., modifying the list. "Select" has the advantage of lacking that connotation. To avoid dissonance with the two perl5 "select"s, we could

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

Juerd wrote: Fagyal Csongor skribis 2006-09-20 11:28 (+0200): You rarely do real HTTP handling when you use CGI. You may not, but many people do a lot of these things. Actually me, too. Not with CGI.pm, though. I tend to use CGI::Simple for form/param parsing, Template.pm for temp

Re: renaming "grep" to "where"

Aaron (>): OK then. Just so that I can type of the final result in S29, let's see if everyone agrees to several points that have been made in this thread: 1. "classify" is the real grep 2. convenience function, "keep" is probably a macro 3. "use List :compat" will get you a "grep" just as it wil

Re: renaming "grep" to "where"

Damian Conway wrote: In other words, classify() takes a list of values, examines each in turn, and ascribes a "label" value to it. The call returns a list of pairs, where each pair key is one of the label values and each pair value is an array of all the list values that were ascribed that labe

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

Thomas Wittek wrote: [...] But I think that it would be a good idea to create a clean, "servlety" foundation, upon which you still can implement a 200 lines CGI.pm/Web.pm/foo.pm that covers the most common web-request tasks. That sounds nice. - Cs.

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

Fagyal Csongor skribis 2006-09-20 11:28 (+0200): > You rarely do real HTTP handling when you use CGI. You may not, but many people do a lot of these things. And when you don't, the datastructures are currently parsed and filled anyway, so I don't know why you say it'd be too inefficient. > A gen

[perl #40370] [PATCH] code_coda.t update

# New Ticket Created by "Paul Cochrane" # Please include the string: [perl #40370] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=40370 > Hi, Attached is a patch for the code_coda.t test. The test now accepts files passed

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

Fagyal Csongor schrieb: > Ian Langworth wrote: > A general, simple CGI handling module fits into 200 lines, including > POD. > > [..] > > You don't really need more. IMHO a CGI module > parses/preprocesses/decodes/etc. all incoming parameters (POST, GET, > COOKIES), and that's it. I can support

call, call(), .call, and captures

From S06: sub bar ($a,$b,$c,:$mice) { say $mice } sub foo (\$args) { say $args.perl; &bar.call($args); } The C<.call> method of C objects accepts a single C object, and calls it without introducing a C frame. And from S12: In addition to C, the special function C dispatches

[svn:perl6-synopsis] r12247 - doc/trunk/design/syn

Author: audreyt Date: Wed Sep 20 03:27:09 2006 New Revision: 12247 Modified: doc/trunk/design/syn/S06.pod Log: * Ditto. Modified: doc/trunk/design/syn/S06.pod == --- doc/trunk/design/syn/S06.pod(original) +++

[svn:perl6-synopsis] r12246 - doc/trunk/design/syn

Author: audreyt Date: Wed Sep 20 03:22:42 2006 New Revision: 12246 Modified: doc/trunk/design/syn/S06.pod Log: * S06: TreyHarris++ pointed out another slurpy-star legacy. Modified: doc/trunk/design/syn/S06.pod == ---

Re: renaming "grep" to "where"

Just to point out that it's probably worth going back and rereading the earlier iterations of this discussion, in December 2002 (subject: "purge: the opposite of grep") and November 2005 (subject: "Classification syntax"). That way, those who repeat history are condemned to study it. ;-) In su

[svn:perl6-synopsis] r12239 - doc/trunk/design/syn

Author: audreyt Date: Wed Sep 20 02:41:02 2006 New Revision: 12239 Modified: doc/trunk/design/syn/S06.pod Log: * S06: As &code.call() is specified to take one single Capture argument, fix the example in which the argument was erroneously flattened. Modified: doc/trunk/design/syn

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

Ian Langworth wrote: It sounds like the name of HTTP is more appropriate: HTTP::Request ...uri, pathinfo, params, method, headers, etc. HTTP::Request::Session ...adds to HTTP::Request to provide session() method HTTP::Response ...response code, content, headers, etc. H

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

Ian Langworth skribis 2006-09-19 19:02 (-0700): > It sounds like the name of HTTP is more appropriate: > HTTP::Request > ...uri, pathinfo, params, method, headers, etc. > (etc) Well, yes and no. HTTP is today's web protocol standard, but may not be with us forever. I was thinking of getting

Re: CGI Session management (was Re: the CGI.pm in Perl 6)

It sounds like the name of HTTP is more appropriate: HTTP::Request ...uri, pathinfo, params, method, headers, etc. HTTP::Request::Session ...adds to HTTP::Request to provide session() method HTTP::Response ...response code, content, headers, etc. HTTP::Response::JSON

Re: renaming "grep" to "where"

Jonathan Lang skribis 2006-09-19 16:39 (-0700): > >Anyway, it's not clear to me that grep always has an exact opposite. > I don't see why it ever wouldn't: you test each item in the list, and > the item either passes or fails. 'select' would filter out the items > that fail the test, while 'reject