Well, currently, test 61 in t/pmc/pmc.t causes an abrupt stop of
the test session with the segfault box popping up. I haven't yet
taken a time to figure out what actually is the cause of trouble,
but I've already detected the precise place where that all happens.
It happens here
void
free_unused_
On Wednesday, November 26, 2003, at 12:29 PM, Larry Wall wrote:
If you contrast it with an explicit try block, sure, it looks better.
But
that's not what I compare it with. I compare it with Perl 5's:
$opus.write_to_file($file) or die "Couldn't write to $file: $!";
That has some known prob
On Wednesday, November 26, 2003, at 01:50 PM, Michael Lazzaro wrote:
my $c = (defined($a) ? $a : $b);
Sorry, P5.
Before the grammar police attack...
my $c = (defined($a) ?? $a :: $b);
Parens for clarity.
MikeL
[EMAIL PROTECTED] (Michael Lazzaro) writes:
> I think we also need to be skeptical of the false economy of putting such
> sugar into CP6AN, if a sizable portion of the community is going to
> download it anyway.
"The standard Perl library will be almost entirely removed. The point of this
is to fo
> > More important -- is the Segfault reported in any other manner. If
> > not, thats bad.
>
> It's not, I'm afraid
Then this shouldn't be off by default.
Turn it off for automated testing. But in general use, I think you
want this on.
"Oh look. My program just went away. I wonder why?"
-R
> At Wed, 26 Nov 2003 05:20:50 +0300,
> Vladimir Lipsky wrote:
> >
> > If it blocks the automated test builds, then just turning the box off is
> > okay. It must be admitted that, the truth is that I don't know anybody
> > who does send those reports
>
> More important -- is the Segfault reported i
On Wednesday, November 26, 2003, at 12:13 PM, chromatic wrote:
On Wed, 2003-11-26 at 11:39, Michael Lazzaro wrote:
I think we also need to be skeptical of the false economy of putting
such sugar into CP6AN, if a sizable portion of the community is going
to download it anyway.
A more interesting q
On 2003-11-26 at 12:13:39, chromatic wrote:
> Consider Perl 5, where File::Find is a core module. While the interface
> may have been nice in 1995 (though I doubt even that), it's been widely
> regarded as awful for at least three years. It's likely never to be
> removed from the core. File::Fin
On Wed, Nov 26, 2003 at 11:39:41AM -0800, Michael Lazzaro wrote:
: On Monday, November 24, 2003, at 03:28 PM, Luke Palmer wrote:
: >Damian Conway writes:
: >>In which case I think we just fall back to:
: >>
: >>try{$opus.write_to_file($file); CATCH {die "Couldn't write to
: >>$file:
: >>$!
On Wed, 2003-11-26 at 11:39, Michael Lazzaro wrote:
> I think we also need to be skeptical of the false economy of putting
> such sugar into CP6AN, if a sizable portion of the community is going
> to download it anyway.
A more interesting question is *when* to put something into the core
language
On Monday, November 24, 2003, at 03:28 PM, Luke Palmer wrote:
Damian Conway writes:
In which case I think we just fall back to:
try{$opus.write_to_file($file); CATCH {die "Couldn't write to
$file:
$!"}}
which is, after all, only 5 characters longer than:
$opus.write_to_file($file) c
Dan Sugalski <[EMAIL PROTECTED]> wrote:
[ a lot of design ]
> Yes, this does bloat out the format some, but it
Seems so. But anyway, can you put together a design document and check
it in, so that this whole stuff isn't lost in history.
Some additional random remarks and questions:
* Where do
- Original Message -
From: "Robert Spier" <[EMAIL PROTECTED]>
To: "perl6-internals" <[EMAIL PROTECTED]>
Sent: Wednesday, November 26, 2003 5:51 AM
Subject: Re: Segfault warning boxes on Win32
> At Wed, 26 Nov 2003 05:20:50 +0300,
> Vladimir Lipsky wrote:
> >
> > If it blocks the automate
13 matches
Mail list logo
