chromatic [EMAIL PROTECTED] writes:
Larry is shockingly good at that synthesis. (Just ask Piers Cawley;
he'll wax eloquent on the subject.)
I'm not sure 'eloquent' is quite the adjective you were looking
for. 'incoherent'?
On Mon, Nov 24, 2003 at 04:40:23PM -0800, Michael G Schwern wrote:
On Mon, Nov 24, 2003 at 05:00:38PM -0700, Luke Palmer wrote:
my $n;
while $n++ then @accum $total {
...
}
(Where I got in trouble for using Cand and never executing anything :-)
To me, it's
Damian Conway writes:
Perhaps this is yet another argument for insisting on:
while do {$n++; $foo $bar}
instead.
Yes please! Is anybody here a fan of the C comma? I don't think I've
ever used it -- well, not intentionally, anyway -- but these are the
situations where I've spotted
Currently it isn't prohibitied. That is the only way to detect an error
from PIO_open* at this time.
io = PIO_open(interpreter, NULL, file[i], flags[j]);
if ( (PIO_eof(interpreter, io) ? 0:1) != expected[i][j] )
{
0x4c56
On Mon, 24 Nov 2003, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
On Mon, 24 Nov 2003, Leopold Toetsch wrote:
In the mean time I've checked in freeze/thaw for PerlHash. It uses an
element count as list does. We could of course use your proposed scheme
Vladimir Lipsky [EMAIL PROTECTED] writes:
Hey unix folks, does test 10 in t/src/io.t succed on your OS?
Yes, I just tested it again.
patch applied.
boe
--
Juergen Boemmels[EMAIL PROTECTED]
Fachbereich Physik Tel: ++49-(0)631-205-2817
Universitaet
Melvin Smith [EMAIL PROTECTED] writes:
At 11:45 AM 11/24/2003 +0300, Vladimir Lipsky wrote:
Hi everyone!
In t/src/io.c, specifically test 9 and 10, I wonder if the PIO_eof check up
works anywhere; because I didn't manage to find any place where the
PIO_F_EOF flag is set up when the
Thies C. Arntzen [EMAIL PROTECTED] writes:
hiya,
still working onm this php-compiler;-)
thanx for all the replies on my last issue..
next question: calling conventions.
in the calling_convertion.pod you say that the callee should
Folks,
I just committed a patch to disable the Your program has crashed, want to
send a report to Microsoft box that pops up on Win32 when Parrot
segfaults -- it blocks the automated test builds which as you might expect
happens with some regularity. :) However I'm not sure if this ought be the
At 05:03 PM 11/25/2003 +0100, Juergen Boemmels wrote:
Melvin Smith [EMAIL PROTECTED] writes:
In PIO_open the ParrotIO object never gets created if there is
an error condition.
But PIO_open returns a valid IO-PMC which just has a NULL in its data
segment. Maybe it should return PMCNULL if the
Hi,
the test in imcc/t/imcpasm/{pcc,optc}.t are currently failing. First I
thought this was a problem with my setup because most tinderbox were
green. It took me a while until I found out that they also fail, but
you need to look in the logs to see it. Is there a bug in the
tinderbox-code?
It my fault. I was messing around with labels. I have a pending
patch to clarify some more things in the API so for now we just
need to disable the imcc/t/imcpasm tests.
Global labels get fixup and are loaded into global table by packfile.
The local labels don't need to be globals.
-Melvin
Simon Cozens [EMAIL PROTECTED] writes:
Luke Palmer:
So modules that introduce new concepts into the language can add new
syntax for them without working with (ugh) a source filter. And some of
these new syntaxes in the core language will actually be in standard
modules, if they're not
On 2003-11-25 at 18:17:04, Piers Cawley wrote:
aString replace: aPattern with: aString.
aString replaceAll: aPattern with: aString.
Stop! Stop that at once! No small talk; we're here for
serious discussions!
:)
Except... the second argument isn't strictly a string because it's
Piers Cawley writes:
Simon Cozens [EMAIL PROTECTED] writes:
But it isn't, and I don't know why it isn't, and so we end up
spending loads of time discussing things that can be punted out to
modules. Designing Perl 6 is hard enough; let's not try to fill
CP6AN at the same time.
But the
Mark J. Reed [EMAIL PROTECTED] writes:
On 2003-11-25 at 18:17:04, Piers Cawley wrote:
aString replace: aPattern with: aString.
aString replaceAll: aPattern with: aString.
Stop! Stop that at once! No small talk; we're here for
serious discussions!
:)
Except... the second
On Mon, 24 Nov 2003, Jonathan Scott Duff wrote:
or maybe throw some latin in there
while $n++ et @accum $total { ... }
while $n++ cum @accum $total { ... } # maybe?
I think ac is the latin conjunction you want.
ac : conj. and, and also, and besides
On 2003-11-25 at 13:46:39, John Williams wrote:
On Mon, 24 Nov 2003, Jonathan Scott Duff wrote:
or maybe throw some latin in there
while $n++ et @accum $total { ... }
while $n++ cum @accum $total { ... } # maybe?
I think ac is the latin conjunction you want.
ac
On Tue, Nov 25, 2003 at 01:03:19PM +1100, Damian Conway wrote:
Schwern observed:
This may be a consequence of the example used
while $n++ then $foo $bar
which I immediately associated with.
if $n++ then $foo $bar
Yeah, I can certainly see that.
Perhaps this is yet
Damian Conway wrote:
Micheal G. Schwern wrote:
It also doesn't convey anything about evaluate the left
hand side, ignore the results and evaluate the right.
I think that's exactly what it conveys:
The suspect drank half a dozen double whiskys then drove
into a lake.
Jonathan Scott Duff wrote:
or maybe throw some latin in there
while $n++ et @accum $total { ... }
while $n++ cum @accum $total { ... } # maybe?
Et, of course, is unsuitable as a direct synonym for and.
I'm afraid that adding the second would cause Perl source code
to
On Tue, Nov 25, 2003 at 01:46:39PM -0700, John Williams wrote:
On Mon, 24 Nov 2003, Jonathan Scott Duff wrote:
or maybe throw some latin in there
while $n++ et @accum $total { ... }
while $n++ cum @accum $total { ... } # maybe?
I think ac is the latin conjunction you
Austin Hastings writes:
-Original Message-
From: Adam Turoff [mailto:[EMAIL PROTECTED]
On Tue, Nov 25, 2003 at 01:03:19PM +1100, Damian Conway wrote:
Schwern observed:
Perhaps this is yet another argument for insisting on:
while do {$n++; $foo $bar}
On Tue, Nov 25, 2003 at 04:48:08PM -0700, Luke Palmer wrote:
Austin Hastings writes:
C style Cfor loops then look like:
for (($a = 0; $b = $num_elts); $a @arry; ($a++; $b -= $offset)) {...}
By which you mean
loop ($a = 0; $b = $num_elts); $a @arry; ($a++; $b -= $offset)
Adam Turoff wrote:
Damian Conway wrote:
Perhaps this is yet another argument for insisting on:
while do {$n++; $foo $bar}
instead.
That looks like syntactic sugar for
while (do) {$n++; $foo $bar}
do is not merely prototyped, but a builtin. With a mandatory {}
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #24553]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24553
Hi,
when checking up on 'imcfaq.pod' I noticed that this file wasn't
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
0x4C56
- Original Message -
From: Dan Sugalski [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 25,
The Perl 6 Summary for the fortnight ending 20031123
Right, hopefully things are back to normal(ish) after the disk crashes
that rather spoilt the last summary. I've managed to fill in my mail
archive too so this summary will cover the events of the last fortnight
(that's two weeks
The Perl 6 Summarizer wrote:
Do Steve Fink's debugging for him
Steve Fink had a problem with some generated code throwing a segfault
when it was run and, having hit the debugging wall himself, posted the
code to the list and asked help. Leo tracked down the bug in Parrot and
fixed
I think separating the IMCC and parrot programming FAQs, or making the
IMCC faq a section of a larger Parrot FAQ, would be better. The IMCC FAQ
really ought to be about syntax rather than semantics.
Patches welcome.
:-J
-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 in any other
Juergen Boemmels [EMAIL PROTECTED] wrote:
No, I think we need to rethink the wrapping technology (which I
introduced). Something like:
struct parrot_io_t {
PObj pobj;
UINTVAL flags;
PIOHANDLE fd;
...
};
But this needs to allocate garbage-collected memory of
sizeof(struct
32 matches
Mail list logo
