On Wed, Oct 05, 2005 at 06:26:17PM -0400, David Golden wrote:
> Michael G Schwern wrote:
> >AFAIK there is only one module of consequence which does screen scraping
> >on Test::More and that's Test::Builder::Tester (Test::Warn, it turns out,
> >fails because of Test::Builder::Tester). Fix that,
On Oct 7, 2005, at 11:17 PM, Michael G Schwern wrote:
I'm absorbing Test::Builder::Tester into the Test-Simple distribution.
This kills three birds with one stone:
- Anyone who updates Test::More gets a fixed Test::Builder::Tester
which should solve most the current problem, unless you use
I'm feeling rather obstinate. I talk about changes on perl-qa. I post
release announcements to here, p5p and module-authors for a reason. All
those modules that this change broke and not a single one of them tried
their module with the Test-Simple alphas and reported the problem. Because
of
On Fri, Oct 07, 2005 at 03:42:57PM -1000, Joshua Hoblitt wrote:
> On Fri, Oct 07, 2005 at 09:34:27AM +0200, Leopold Toetsch wrote:
> > [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > > Modified:
> > >trunk/config/init/hints/linux.pl
> > > Log:
> > > Defined _X_OPEN_SOURCE=600 in ccflags t
On Fri, Oct 07, 2005 at 12:50:09 -0700, chromatic wrote:
> On Fri, 2005-10-07 at 12:49 +0200, Juerd wrote:
>
> > Ashley Winters skribis 2005-10-06 19:30 (-0700):
>
> > > > my Array $a = 97; # dies eventually, but when?
> > > Runtime -- cannot coerce Int value to Array
>
> > It is fully
On Fri, Oct 07, 2005 at 10:28:13 -0400, Austin Hastings wrote:
> But the point is that "resuming from an exception" (or
> appearing to) is not bound to "implemented with continuations".
What's the point?
Continuations are good for exactly this purpose. Parrot already
supports them. I see absolut
On 10/7/05, chromatic <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-10-07 at 17:43 -0600, Luke Palmer wrote:
>
> > No, you can't overload assignment at runtime because you can't
> > overload assigment at any time, so says the language spec (well, not
> > any formal spec; so says Larry as far as I remem
On Fri, Oct 07, 2005 at 09:34:27AM +0200, Leopold Toetsch wrote:
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> > Modified:
> >trunk/config/init/hints/linux.pl
> > Log:
> > Defined _X_OPEN_SOURCE=600 in ccflags to fix implicit POSIX function
> > declaration warnings when compiling src/
On Wed, 2005-10-05 at 23:53 -1000, Joshua Hoblitt wrote:
> I attempted to mechanize Pod generation from RT tickets this morning and
> ran into what I suspect is a bug in the RT client. Why don't we just
> commit BROKEN as is, make a note about it in RELEASE_INSTRUCTIONS, and
> plan on moving towa
On Fri, 2005-10-07 at 17:43 -0600, Luke Palmer wrote:
> No, you can't overload assignment at runtime because you can't
> overload assigment at any time, so says the language spec (well, not
> any formal spec; so says Larry as far as I remember).
I'm wearing my "just a programmer, not a denizen of
On 10/7/05, Luke Palmer <[EMAIL PROTECTED]> wrote:
> On 10/7/05, chromatic <[EMAIL PROTECTED]> wrote:
> > On Fri, 2005-10-07 at 15:22 -0600, Luke Palmer wrote:
> > > But you are allowed to overload coersion. Essentially, every
> > > expression gets a coerce:($expr, $current_context) wrapped around
On 10/7/05, chromatic <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-10-07 at 15:22 -0600, Luke Palmer wrote:
> > But you are allowed to overload coersion. Essentially, every
> > expression gets a coerce:($expr, $current_context) wrapped around
> > it (where these are optimized away when they do nothin
On Fri, 2005-10-07 at 15:22 -0600, Luke Palmer wrote:
> On 10/7/05, chromatic <[EMAIL PROTECTED]> wrote:\
> > If I added a multisub for Array assignment so that assigning an integer
> > value set the length of the array, would 97 be compatible with Array?
> You're not allowed to overload assignm
# New Ticket Created by "Erick"
# Please include the string: [perl #37381]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37381 >
This transaction appears to have no content
On Fri, Oct 07, 2005 at 03:46:02PM -0600, Luke Palmer wrote:
> Uh no. Okay, when I said that they "don't close", I guess I meant
> they don't close like anonymous routines do. It works precisely like
> Perl 5's:
>
> sub foo {
> my $foo = 5;
> sub bar {
> return $f
On 10/7/05, Juerd <[EMAIL PROTECTED]> wrote:
> Luke Palmer skribis 2005-10-07 15:31 (-0600):
> > sub foo($x) {
> > sub bar() {
> > return $x;
> > }
> > return &bar;
> > }
> > foo(42).(); #
>
> Does this mean that this Perl 5 snippet no longer d
Luke Palmer skribis 2005-10-07 15:31 (-0600):
> Well, I see a cognitive downside. That is, package declarations (the
> default) don't create closures. It's like this:
> sub foo($x) {
> sub bar() {
> return $x;
> }
> return &bar;
> }
> foo(42).();
On 10/7/05, Juerd <[EMAIL PROTECTED]> wrote:
> Miroslav Silovic skribis 2005-10-07 13:07 (+0200):
> > Can an inline role be named?
> > 0 but role is_default {}
>
> This is a nice idea. It would require named roles (and to really be
> succesful, also classes, subs, methods, ...) declarations to be
>
On 10/7/05, chromatic <[EMAIL PROTECTED]> wrote:\
> If I added a multisub for Array assignment so that assigning an integer
> value set the length of the array, would 97 be compatible with Array?
You're not allowed to overload assignment.
But you are allowed to overload coersion. Essentially, ev
On Oct 7, 2005, at 20:52, Andy Dougherty wrote:
perl Configure.pl --optimize=-O3 --debugging=0 --cc=gcc --ld=gcc
--link=gcc
...
Andy slowly please. No --optimize tests yet. Let's first look at plain
default build.
Intel x86/gcc-3.3.5, built with
perl Configure.pl --optimize=
The BASIC compiler is now (kind of?) working again after the 0.3.0
release. Updates to the new calling conventions. No longer trying to
manage the conventions in near-PASM level code.
The windows display code is just commented out, but several of the
samples in the compiler (inc. conn4, han
chromatic skribis 2005-10-07 12:50 (-0700):
> > > > my Array $a = 97; # dies eventually, but when?
> > > Runtime -- cannot coerce Int value to Array
> > It is fully determinable at compile time. 97 will never be compatible
> > with Array, so I see no reason to wait.
> If I added a multisub
On Fri, 2005-10-07 at 12:49 +0200, Juerd wrote:
> Ashley Winters skribis 2005-10-06 19:30 (-0700):
> > > my Array $a = 97; # dies eventually, but when?
> > Runtime -- cannot coerce Int value to Array
> It is fully determinable at compile time. 97 will never be compatible
> with Array, s
On Thu, 6 Oct 2005, Leopold Toetsch via RT wrote:
> Leopold Toetsch wrote:
>
> > ... When now this pointer (ctx.rctx) is
> > declared being 'void *' it should be compatible with any other pointer
> > to a structure.
>
> I've now rewritten the questioanable code to use a (void*) allocation
> p
> [jonathan - Di 04. Okt 2005, 15:03:03]:
>
> After a show of demand for here docs on IRC (and leo's approval), I've
> now modified to lexer to support them. The syntax for introducing a
> heredoc is <<"XXX", and it ends on the line containing (only) XXX. For
> example:-
>
Thanks a lot Jonathan.
Yuval Kogman wrote:
>On Fri, Oct 07, 2005 at 02:31:12 -0400, Austin Hastings wrote:
>
>
>>Yuval Kogman wrote:
>>
>>
>>
>>>Stylistically I would tend to disagree, actually. I think it's cleaner to
>>>use exception handling for this.
>>>
>>>Also, this implies that you know that the errors are
Miroslav Silovic skribis 2005-10-07 13:07 (+0200):
> Can an inline role be named?
> 0 but role is_default {}
This is a nice idea. It would require named roles (and to really be
succesful, also classes, subs, methods, ...) declarations to be
expressions, but I see no downside to that.
Juerd
--
h
HaloO
Yuval Kogman wrote:
We have:
die: throw immediately
fail: return an unthrown exception, which will be thrown
depending on whether our caller, and their caller - every scope
into which this value propagates - is using fatal.
This is enough for normal excep
Joshua Gatcomb wrote:
--- Joshua Hoblitt via RT
<[EMAIL PROTECTED]> wrote:
Can you still recreate this issue?
I haven't been involved in Parrot development for some
time now. When I was involved I was pretty much the
only Cygwin user actively participating so it was
frustrating not
Yuval Kogman wrote:
c) not all the tests were converted, and the script written to
convert them is now lost, afaict
The original 2-part script is available from my homepage at
http://laire.info/markus/perl/re_tests.html
Still, I'm not sure if that's of any use anymore.
--
Mark
On Fri, 2005-10-07 at 09:34 +0200, Leopold Toetsch wrote:
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> > Modified:
> >trunk/config/init/hints/linux.pl
> > Log:
> > Defined _X_OPEN_SOURCE=600 in ccflags to fix implicit POSIX function
> > declaration warnings when compiling src/platf
AmethystSHEVEK
Apache-ACEProxy MIYAGAWA
Apache-DoCoMoProxy KOBAYASI
Apache-Gallery LEGART
Apache-No404Proxy MIYAGAWA
[...the long list of modules continues...]
This list came from CPANTS, right? I think there's something screwy
with the way it's following dependencies.
[EMAIL PROTECTED] wrote:
Would this work too?
0 but role {}
Most certainly, but you would have no way to refer to that role later,
so it is questionable how useful that construct is. No, it's not
questionable. That is a useless construct.
Luke
Can an inline role be named?
0 b
[EMAIL PROTECTED] wrote:
I'm not bashing your idea, because I think it has uses. But I'll
point out that all of these can be easily accompilshed by writing a
wrapper for open(). That would be the usual way to abstract this kind
of thing.
My take on this: resumable exceptions break encaps
On Fri, Oct 07, 2005 at 17:07:09 +0200, Yuval Kogman wrote:
> Hi,
>
> I wrote a script that parses our semi converted rules.t file from
> pugs to parrot.
I forgot to say where it is:
http://svn.openfoundry.org/pugs/throw_away/
this includes the converter, and the rules.t file split into chunks
o
Hi,
I wrote a script that parses our semi converted rules.t file from
pugs to parrot.
This script can grok all the constructs in use right now, and emit
equivalent perl 5 code.
Given another few hours of work I can make the perl emission code
into a Test::Base backend to retain portability.
The
Yuval Kogman skribis 2005-10-07 12:53 (+0200):
> On Fri, Oct 07, 2005 at 12:42:01 +0200, Juerd wrote:
> > For my Int $c = $float, though, I'd want coercion.
> > And I think it is wrong to have such a huge difference between literals
> > and values: if a variable coerces, a literal has to do so too.
Ashley Winters skribis 2005-10-06 19:30 (-0700):
> > my Array $a = 97; # dies eventually, but when?
> Runtime -- cannot coerce Int value to Array
It is fully determinable at compile time. 97 will never be compatible
with Array, so I see no reason to wait.
Do remember that some programs r
On Fri, Oct 07, 2005 at 12:42:01 +0200, Juerd wrote:
> For my Int $c = $float, though, I'd want coercion.
>
> And I think it is wrong to have such a huge difference between literals
> and values: if a variable coerces, a literal has to do so too.
How do you tell the compiler "this must never be a
Yuval Kogman skribis 2005-10-07 3:02 (+0200):
> > my Array $a = 97; # dies eventually, but when?
> > my Int $b = 3.1415; # dies at all?
> Both die at compile time, because the user explicitly contradicted
> him/herself. This is like saying
> my int = $x :: float;
For my Int
On Fri, Oct 07, 2005 at 05:23:55 +0100, Piers Cawley wrote:
> "Peter Haworth" <[EMAIL PROTECTED]> writes:
>
> > On Wed, 5 Oct 2005 19:24:47 +0200, Yuval Kogman wrote:
> >> On Wed, Oct 05, 2005 at 16:57:51 +0100, Peter Haworth wrote:
> >> > On Mon, 26 Sep 2005 20:17:05 +0200, TSa wrote:
> >> > > Pi
On Fri, Oct 07, 2005 at 02:31:12 -0400, Austin Hastings wrote:
> Yuval Kogman wrote:
>
> >On Thu, Oct 06, 2005 at 14:27:30 -0600, Luke Palmer wrote:
> >
> >
> >>On 10/6/05, Yuval Kogman <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >>>when i can't open a file and $! tells me why i couldn't
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #37372]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37372 >
charset/unicode.c needs implementation of is_ccass / find_cclass, /
find_not_cclass
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #37371]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37371 >
During opcode cleanup the find_word_boundary opcode ceased to exist
(there was no i
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Modified:
>trunk/config/init/hints/linux.pl
> Log:
> Defined _X_OPEN_SOURCE=600 in ccflags to fix implicit POSIX function
> declaration warnings when compiling src/platform.c.
> +if ( $cflags !~ /-D_XOPEN_SOURCE=/ ) {
> +# Request visib
45 matches
Mail list logo
