Re: Lessons from the test function parameter placement quibbles?

* Michael G Schwern <[EMAIL PROTECTED]> [2006-07-19 02:10]: > On 7/17/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote: > >Had they been named parameters, we wouldn't be having this > >discussion. > >is got => 'foo', expected => 'bar', description => 'foo is bar'; > >is 'foo', 'bar', 'foo is ba

Re: Re: Checkin #13345

chromatic <[EMAIL PROTECTED]> wrote: On Tuesday 18 July 2006 19:43, Matt Diephouse wrote: > I know I'm a little late to the game here, but in the future it would > be useful to mention this sort of info in a comment in the source. :-) > And a comment might be a nice addition even now. > > (You m

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

[EMAIL PROTECTED] writes: > New Revision: 10299 > > Modified: doc/trunk/design/syn/S03.pod > == > > +If the next item after the list operator is either an infix operator > +or a term, a syntax error. If the sentence has

Re: [CAGE] Coverity and Splint: Has anyone started using these with Parrot?

On Wed, Jul 12, 2006 at 12:54:30AM -0500, Andy Lester wrote: > I think the very first thing we ought to do is start working on > turning up the warnings levels in gcc as much as we can, and add as > many warnings flags as we can. gcc at least is pretty standard and > we can all use it. con

Re: Hyperoperators and the Each role

On Mon, Jul 17, 2006 at 06:06:52PM -0400, Christopher Jeris wrote: : I have a couple of questions about what S03 says about hyperoperators : applying recursively to any object which matches the 'Each' role: : : [from S03] : Seq(3,8,[2,Seq(9,3)],8) >>-<< (1,1,2,1); # Seq(2,7,[0,Seq(7,1)],7) : : 1.

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

Author: larry Date: Tue Jul 18 20:26:43 2006 New Revision: 10299 Modified: doc/trunk/design/syn/S02.pod doc/trunk/design/syn/S03.pod Log: Tightening up deceptive syntaxes a bit. Modified: doc/trunk/design/syn/S02.pod

Re: Checkin #13345

On Tuesday 18 July 2006 19:43, Matt Diephouse wrote: > I know I'm a little late to the game here, but in the future it would > be useful to mention this sort of info in a comment in the source. :-) > And a comment might be a nice addition even now. > > (You mentioned being more clear in the svn lo

Re: Checkin #13345

chromatic <[EMAIL PROTECTED]> wrote: ... provides quite misleading results: $ parrot -o file.pir Option file.pir expects an argument parrot -[abcCEfgGhjprStvVwy.] [-d [FLAGS]] [-O [level]] [-o FILE] I don't believe there's a working heuristic for guessing which parameter the user failed to pro

Re: Lessons from the test function parameter placement quibbles?

On Tuesday 18 July 2006 17:28, Jonathan Rockway wrote: > If you really don't want to have test names, you can specify undef. But > making them "required" (as in "before everything else") makes the API > easier to use for people who are doing things right (i.e. naming their > tests). That's beggi

Re: Tap Streams

Ovid wrote: Hi all, Just a quick question, mainly aimed at Schwern since he's most familiar with TAP::Harness, though others with thoughts should definitely chime in. To handle streams, I am thinking of this: my $parser = TAPx::Parser->new; while ( defined ( my $chunk = $tap_stream->next

Re: Lessons from the test function parameter placement quibbles?

> I'd like test names to be more widespread, but I really don't want > them mandatory. If you really don't want to have test names, you can specify undef. But making them "required" (as in "before everything else") makes the API easier to use for people who are doing things right (i.e. naming th

Re: use Tests; # ?

On 7/17/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: I know we've moved on, but I'm in a completely different time zone, so please understand... I, like demerphq, also think that coming up with a name for each and every test is a good idea. It shouldn't be hard to think of a description f

Re: use Tests; # ?

On 7/17/06, demerphq <[EMAIL PROTECTED]> wrote: > Well, if the test passes, there's no need to know where exactly it's > located. If it fails, the diagnostics contain the line number: > > not ok 6 > # Failed test in t/xxx.t at line 26. > > I've never seen incorrect line numbers. I have. L

Re: Lessons from the test function parameter placement quibbles?

On 19/07/06, Michael G Schwern <[EMAIL PROTECTED]> wrote: On 7/17/06, demerphq <[EMAIL PROTECTED]> wrote: > IMO the best way to do that is to make test names mandatory. The file and line number provided by the failing test isn't enough to find it? Not always, but even so, mandatory test names i

Re: Lessons from the test function parameter placement quibbles?

On 7/17/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote: so by now we've had quibbles about the "irregularity" of `skip`, `can_ok` and `isa_ok`, and a suggestion that the test name always go first. This puts the emphesis on the wrong thing. The point of the test is the test, not the description. D

Re: Lessons from the test function parameter placement quibbles?

On 7/17/06, demerphq <[EMAIL PROTECTED]> wrote: Just to clarify, my main point is really that test names should be mandatory. The fact that making them mandatory also solves other problems is to me mostly a nice bonus. What I really want is that when I try to build something and it fails test tha

Re: Checkin #13345

On Tuesday 18 July 2006 13:38, Audrey Tang wrote: > Chromatic: Your original commit log noted room for possible > improvements with the English > message, which I interpreted as a invitation to help, and acted > accordingly, but probably > was mistaken, and thereby perceived as rude. I'm sorry ab

Re: Kwalitee metric: Broken Installer

On Tuesday 18 July 2006 15:57, Jonathan Rockway wrote: > 2) Get M::I into the core of perl, so that everyone has a known-good > tested-everywhere version. For various values of "everyone" and "everywhere" perhaps. > Actually now I see a third resolution: don't use M::I for CPAN modules. > CPAN (

Re: Kwalitee metric: Broken Installer

I see two resolutions to this problem: 1) Module authors need to re-release their modules whenever Module::Install is updated. This is extremely inconvenient, but not a terrible demand. If other authors are like me, they accumulate small minor changes to their modules, and then release when

Real Kwalitee, or please stop spending time thinking about CPANTS

At this point, CPANTS rules are getting into the realm of purely self- pleasuring. If more than a dozen people outside of this small enclave of people cares whether a module gets a 16 or 17, I'll be shocked. I have a couple of suggestions on ways you can make REAL kwalitee changes and p

Re: Kwalitee metric: Broken Installer

Steffen Mueller wrote: Hi domm, hi perl.qa, we had a discussion about distributions with broken versions of Module::Install. Using Module::CPANTS::Kwalitee::* as models I wrote a simple plugin that calculates a Kwalitee metric "uses_broken_installer". - If the distribution doesn't use Module

Re: Kwalitee metric: Broken Installer

* Randy W. Sims <[EMAIL PROTECTED]> [2006-07-19 00:20]: > For example, who's to say what constitutes a bad version of an > installer How about the installer maintainer himself? As in the case of M::I… Regards, -- Aristotle Pagaltzis //

Re: [perl #39853] [BUG] Tcl - pwd returns path with backslashes on Win32

Will Coleda wrote: > Since both tcl and perl seem to like this style (but I'm sure some > languages need truly native representations), I'd propose that the OS > PMC give a way to say which is preferred. I agree. As another note, many programs are fine with forward slashes, including Microsoft's

Re: [perl #39868] [CAGE] convert C

Note: there are some tests where the number of tests cannot be determined until runtime (and therefore don't have "BEGIN" blocks tied to them.) These (like t/doc/pod.t) need to be preserved. On Jul 18, 2006, at 5:47 PM, Jerry Gay (via RT) wrote: some test files were converted to use begin

[perl #39868] [CAGE] convert C NN; }> to C NN;>

# New Ticket Created by Jerry Gay # Please include the string: [perl #39868] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=39868 > some test files were converted to use begin blocks at the bottom of the test file. this doe

Re: another item for the cage list: INTVAL_MAX etc.

updated the ticket to say [CAGE], which makes it show on the RT list for [CAGE] tickets, http://xrl.us/owsd (from cage/todo.pod in the repo.) Regards. On Jul 18, 2006, at 4:51 PM, Chip Salzenberg wrote: (I'd have added this myself, Andy, but you're the keeper of the cage/todo.pod document s

Re: [perl #39867] Configure.perl --maintainer should check flex/bison versions

On Tue, Jul 18, 2006 at 10:48:45AM -1000, Joshua Hoblitt wrote: > I believe ambs & I fixed this before the bug was filed. ;) Bugs fixed before they're filed? Now _that's_ a process failure mode I can live with! :-) -- Chip Salzenberg <[EMAIL PROTECTED]>

another item for the cage list: INTVAL_MAX etc.

(I'd have added this myself, Andy, but you're the keeper of the cage/todo.pod document structure.) New thing: RT #39855: configuration: define MIN/MAX macros for all integral typedefs For example, if INTVAL is long, then config.h should include: #include #define INTVAL_MIN LONG_MIN

Re: [perl #39867] Configure.perl --maintainer should check flex/bison versions

I believe ambs & I fixed this before the bug was filed. ;) -J -- On Tue, Jul 18, 2006 at 01:31:16PM -0700, Chip Salzenberg wrote: > # New Ticket Created by Chip Salzenberg > # Please include the string: [perl #39867] > # in the subject line of all future correspondence about this issue. > # h

Re: Checkin #13345

在 2006/7/18 下午 3:55 時，jerry gay 寫到： On 7/18/06, chromatic <[EMAIL PROTECTED]> wrote: On Tuesday 18 July 2006 02:21, Audrey Tang wrote: > Does r13347 look better? If not, please revert both my changes. I think it's still misleading. #13364 is probably as accurate as Parrot can report. a

[perl #39867] Configure.perl --maintainer should check flex/bison versions

# New Ticket Created by Chip Salzenberg # Please include the string: [perl #39867] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=39867 > Currently if the user has bison or flex that's too old, he won't be told, and will si

Re: Checkin #13345

On Tuesday 18 July 2006 12:55, jerry gay wrote: > On 7/18/06, chromatic <[EMAIL PROTECTED]> wrote: > > On Tuesday 18 July 2006 02:21, Audrey Tang wrote: > > > Does r13347 look better? If not, please revert both my changes. > > I think it's still misleading. #13364 is probably as accurate as Par

[perl #39866] segfaulting command line options.

# New Ticket Created by Will Coleda # Please include the string: [perl #39866] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=39866 > >> this still segfaults: >> >> ./parrot -D 1 >> >> as does this: >> >> ./parr

Re: Checkin #13345

On 7/18/06, chromatic <[EMAIL PROTECTED]> wrote: On Tuesday 18 July 2006 02:21, Audrey Tang wrote: > Does r13347 look better? If not, please revert both my changes. I think it's still misleading. #13364 is probably as accurate as Parrot can report. and has the distinction of compiling on win

Re: Checkin #13345

On Tuesday 18 July 2006 02:21, Audrey Tang wrote: Hi Audrey, > Does r13347 look better? If not, please revert both my changes. I think it's still misleading. #13364 is probably as accurate as Parrot can report. > As an aside, regardless of the three changes, this still segfaults: > > ./

Re: [perl #39853] [BUG] Tcl - pwd returns path with backslashes on Win32

Since both tcl and perl seem to like this style (but I'm sure some languages need truly native representations), I'd propose that the OS PMC give a way to say which is preferred. On Jul 17, 2006, at 8:58 AM, Ron Blaschke (via RT) wrote: # New Ticket Created by Ron Blaschke # Please includ

Re: flex/bison version for Parrot?

在 2006/7/18 下午 1:41 時，Chip Salzenberg 寫到： What versions of flex and bison will work now? I'd like to make Configure.perl (or perhaps the Makefile at runtime?) choke on -- maintainer if the right versions aren't found. Flex 2.5.33, Bison 2.2. Thanks, Audrey PGP.sig Description: This is

flex/bison version for Parrot?

What versions of flex and bison will work now? I'd like to make Configure.perl (or perhaps the Makefile at runtime?) choke on --maintainer if the right versions aren't found. -- Chip Salzenberg <[EMAIL PROTECTED]>

get_root_namespace opcode vs. interpinfo {cage cleaners?}

Allison, I suppose that given get_root_namespace, that we should get rid of C? If that's true, then a good little cleanup task would be removing all usage of the latter and replacing it with the former. -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [svn:parrot] r13343 - trunk/compilers/imcc

Audrey Tang wrote: This is not a maintainable build solution. Revert and come back when you have one. Please clarify: What, exactly, is not maintainable? The presence of a .diff file, or the fact that it needs to be applied manually? Both. Assuming both were considered unmaintainable, fixe

Tap Streams

Hi all, Just a quick question, mainly aimed at Schwern since he's most familiar with TAP::Harness, though others with thoughts should definitely chime in. To handle streams, I am thinking of this: my $parser = TAPx::Parser->new; while ( defined ( my $chunk = $tap_stream->next ) ) { my

Re: Kwalitee metric: Broken Installer

Hi, Thomas Klausner schrieb: On Tue, Jul 18, 2006 at 12:27:30PM +0200, Steffen Mueller wrote: we had a discussion about distributions with broken versions of Module::Install. Using Module::CPANTS::Kwalitee::* as models I wrote a simple plugin that calculates a Kwalitee metric "uses_broken_inst

[perl #39860] [TODO] build - Configure.pl should accept --libdir, etc.

# New Ticket Created by Joshua Hoblitt # Please include the string: [perl #39860] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=39860 > LIB_DIR gets setup as part of the configure process which is then passed to the instal

Re: [perl #39857] [PATCH] Made httpd.pir RFC compliant (at least about CRLF)

Am Montag, 17. Juli 2006 22:31 schrieb Kay-Uwe Huell: > this is a patch to make examples/io/httpd.pir RFC compliant (at least > about CRLF). Thanks, applied - r13353. leo

Re: Kwalitee metric: Broken Installer

Thomas Klausner wrote: I think it's a good metric, but maybe Module::Install-supports will disagree :-) Well, as long as it only picks up *certain* versions, that's probably OK. We could also add checks for problems in Makefile.PL/Build.PL... At the risk of going out on a limb here, maybe s

Re: Kwalitee metric: Broken Installer

Hi! On Tue, Jul 18, 2006 at 12:27:30PM +0200, Steffen Mueller wrote: > we had a discussion about distributions with broken versions of > Module::Install. Using Module::CPANTS::Kwalitee::* as models I wrote a > simple plugin that calculates a Kwalitee metric "uses_broken_installer". Cool! May

Re: [svn:parrot] r13343 - trunk/compilers/imcc

在 2006/7/18 上午 6:21 時，Audrey Tang 寫到： 在 2006/7/18 上午 5:24 時，Audrey Tang 寫到： 在 2006/7/18 上午 4:38 時，Allison Randal 寫到： This is not a maintainable build solution. Revert and come back when you have one. Please clarify: What, exactly, is not maintainable? The presence of a .diff file, or the

Kwalitee metric: Broken Installer

Hi domm, hi perl.qa, we had a discussion about distributions with broken versions of Module::Install. Using Module::CPANTS::Kwalitee::* as models I wrote a simple plugin that calculates a Kwalitee metric "uses_broken_installer". - If the distribution doesn't use Module::Install, it's fine for

Re: [perl #39856] TODO: Produce Single PBC from Multiple PIR Files with -o

Am Montag, 17. Juli 2006 21:11 schrieb chromatic: > > After discussing the idea with Allison, we both believe that Parrot should > be able to produce a single PBC file from a command like: > > parrot -o all_files.pbc file1.pir file2.pir ... filen.pir Well, that exists already and is named p

Re: [svn:parrot] r13343 - trunk/compilers/imcc

在 2006/7/18 上午 5:24 時，Audrey Tang 寫到： 在 2006/7/18 上午 4:38 時，Allison Randal 寫到： This is not a maintainable build solution. Revert and come back when you have one. Please clarify: What, exactly, is not maintainable? The presence of a .diff file, or the fact that it needs to be applied manua

Re: [svn:parrot] r13343 - trunk/compilers/imcc

在 2006/7/18 上午 4:38 時，Allison Randal 寫到： This is not a maintainable build solution. Revert and come back when you have one. Please clarify: What, exactly, is not maintainable? The presence of a .diff file, or the fact that it needs to be applied manually? If the latter, an extra line of

Re: Checkin #13345

在 2006/7/18 上午 4:49 時，chromatic 寫到： I don't believe there's a working heuristic for guessing which parameter the user failed to provide. That's why I didn't write the original version that way. Does r13347 look better? If not, please revert both my changes. As an aside, regardless of th

[perl #39856] TODO: Produce Single PBC from Multiple PIR Files with -o

# New Ticket Created by chromatic # Please include the string: [perl #39856] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=39856 > After discussing the idea with Allison, we both believe that Parrot should be able to prod

Re: [svn:parrot] r13343 - trunk/compilers/imcc

在 2006/7/18 上午 4:38 時，Allison Randal 寫到： [EMAIL PROTECTED] wrote: This is not a maintainable build solution. Revert and come back when you have one. Reverted. Audrey PGP.sig Description: This is a digitally signed message part

[perl #39857] [PATCH] Made httpd.pir RFC compliant (at least about CRLF)

# New Ticket Created by Kay-Uwe Huell # Please include the string: [perl #39857] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=39857 > Hi parrot, this is a patch to make examples/io/httpd.pir RFC compliant (at least about

Re: [svn:parrot] r13343 - trunk/compilers/imcc

On Tue, Jul 18, 2006 at 01:38:20AM -0700, Allison Randal wrote: > [EMAIL PROTECTED] wrote: > > > >* However, the bison interface does not support both "interp" > > and "yyscanner" as flex inputs; so I created a patch file > > at compiler/imcc/imcparser.c.diff -- it needs to be applied > > manual

Checkin #13345

This patch: --- trunk/compilers/imcc/main.c (original) +++ trunk/compilers/imcc/main.c Tue Jul 18 01:33:59 2006 @@ -369,7 +369,7 @@ exit(EX_USAGE); } if (*argc == opt.opt_index ) { -fprintf(stderr, "Missing option value or program name\n"); +fprintf(stderr, "Opti

Re: [svn:parrot] r13343 - trunk/compilers/imcc

[EMAIL PROTECTED] wrote: * However, the bison interface does not support both "interp" and "yyscanner" as flex inputs; so I created a patch file at compiler/imcc/imcparser.c.diff -- it needs to be applied manually whenever imcc.y is regenerated into imcparser.c. This is really suboptima

Re: [perl #39856] TODO: Produce Single PBC from Multiple PIR Files with -o

On Mon, Jul 17, 2006 at 12:11:55PM -0700, chromatic wrote: > After discussing the idea with Allison, we both believe that Parrot should be > able to produce a single PBC file from a command like: > > parrot -o all_files.pbc file1.pir file2.pir ... filen.pir It'd probably make sense to defi

[perl #39858] [PATCH] more elegant hex_to_int in examples/io/httpd.pir

# New Ticket Created by Kay-Uwe Huell # Please include the string: [perl #39858] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=39858 > Hi parrot, here is a more elegant function for 'hex_to_int' in examples/io/httpd.pir.

[perl #39853] [BUG] Tcl - pwd returns path with backslashes on Win32

# New Ticket Created by Ron Blaschke # Please include the string: [perl #39853] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=39853 > Test languages/tcl/t/cmd_pwd.t fails on Win32. Tcl's pwd returns the path with backslas

Re: IMCC Reentrancy

Audrey Tang wrote: Indeed, and I'd like to apologize publicly for the snipping. Accepted and forgiven. However, the re2c or regel-based scanner refactoring isn't different from a "flex upgrade patch", as it (by definition) can't affect IMCC's public API at all. An additional advantage is t

Re: IMCC Reentarancy

Vishal, 在 2006/7/16 下午 11:57 時，Vishal Soni 寫到： a. Remove flex and implement re2c b. Remove static and global variables Now that the flex part is done, are you still willing to help removing the remaining static/global state? Apart from this we also need to refactor the code to get

Re: IMCC Reentrancy

在 2006/7/18 上午 1:54 時，Audrey Tang 寫到： If you have a way to make IMCC reentrant that involves upgrading to a more recent version of flex and passing one additional parameter, go for it! Send us a patch and if it passes all the tests, we'll apply it. As flex 2.5.30+ is not API compatible wi