On Jul 24, chromatic wrote:
> On Thursday, July 24, 2003, at 05:28 PM, Benjamin Goldberg wrote:
> >If this were Java, the way to do this would be to define a Thingie
> >interface, and then an (archetypical) ThingieObject class... any time
> >that we want to actually *create* Thingies, we would use
# New Ticket Created by "Arcady Goldmints"
# Please include the string: [perl #23115]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=23115 >
Contrary to popular belief, linux does run on things other than x86, and people wi
Andrew P's test program does indeed "work" with Perl 5.8.0
on both Unix and Windows with a test name of 'sample.t' in
THDriver.pl, yet changing it to './sample.t' results in a
failure of: Can't call method "SUPER::runtests" without a
package or object reference. But why?
The snippet below (tested
On Thursday, July 24, 2003, at 05:28 PM, Benjamin Goldberg wrote:
If this were Java, the way to do this would be to define a Thingie
interface, and then an (archetypical) ThingieObject class... any time
that we want to actually *create* Thingies, we would use "new
ThingieObject", but everywhere el
K Stol wrote:
>
> - Original Message -
> From: "Michal Wallace" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, July 23, 2003 4:48 PM
> Subject: approaching python
>
> >
> > Hey all,
> >
> > I've been thinking about the "compiling python to
> > parrot" concept. Right now
What kind of semantics do we want for perl6, if we have:
my $fh1 = fdopen( $n );
do {
my $fh2 = fdopen( $n );
};
# is $fh1 valid or not at this point?
For that matter, what about:
for(1..2) {
my $fh = fdopen( $n ); # does this succed the second time?
}
Should thes
Chromatic wrote:
[snip]
> > I think you want to declare "I comply with ruleset X" at the callee
> > object level. That enables the compiler to (1) check that you're not
> > lying; and (2) optimize based on (1).
>
> At least one of us is using "caller/callee" in the X11 sense. What I
> mean and wh
On Thu, Jul 24, 2003 at 10:55:42AM -0600, Nick Pinckernell wrote:
> I agree with the first three items right out of
> http://dev.perl.org/rfc/5.pod
> 1. IT'S NOT INTUITIVE
"Intuitive" is one of those meaningless buzzwords like "maintainable".
It sounds good, but it's meaningless. See MJD's ta
On Tue, Jul 22, 2003 at 11:41:25PM -0400, Dan Sugalski wrote:
> First, to get it out of the way, I don't have to convince you of
> anything. You have to convince me. For better or worse I'm
> responsible for the design and its ultimately my decision. If you
> don't want async IO, it's time to ma
Luke Palmer wrote:
>Klass-Jan Stol writes:
>
>>>The thing is, I don't have a lot of experience when it comes to
>>>compilers, but I do know a whole lot about python. :) If this
>>>approach makes sense, is there someone with IMCC experience who'd
>>>be willing to do some virtual pair programming wi
On Jul 24, David Wheeler wrote:
> On Wednesday, July 23, 2003, at 05:57 PM, chromatic wrote:
>
> >The first is a deeper question -- besides inheritance, there's
> >delegation, aggregation, and reimplementation (think mock objects)
> >that can make two classes have equivalent interfaces. I'd li
--- chromatic <[EMAIL PROTECTED]> wrote:
> On Thursday, July 24, 2003, at 11:17 AM, Austin Hastings wrote:
>
> >> No, I think Java interfaces are a kluge to get around copying a
> >> broken type system and the lack of multiple inheritance.
> >
> > Multiple Inheritance != Protocols | Interfaces
>
On Thursday, July 24, 2003, at 11:17 AM, Austin Hastings wrote:
No, I think Java interfaces are a kluge to get around copying a
broken type system and the lack of multiple inheritance.
Multiple Inheritance != Protocols | Interfaces
I quite agree, but I've done enough Java to know that if they coul
It now builds and tests fine.
Simon
On Thursday 24 July 2003 16:13, Simon Glover wrote:
> On Thu, 24 Jul 2003, Daniel Grunblatt wrote:
> > On Thursday 24 July 2003 15:55, Juergen Boemmels wrote:
> > > Magic: 7f 45 4c 46 01 01 01
> >
> > 00
> > --
> > 00 00 00 00 00 00 00 00
> >
> > > OS/ABI:UNIX - Sy
On Thu, 24 Jul 2003, Daniel Grunblatt wrote:
> On Thursday 24 July 2003 15:55, Juergen Boemmels wrote:
> > Magic: 7f 45 4c 46 01 01 01
> 00
> --
> 00 00 00 00 00 00 00 00
>
> > OS/ABI:UNIX - System V
>
> Patch is in, please resync and try it.
>
It's now dieing
On Thu, 24 Jul 2003, Joseph F. Ryan wrote:
> I'm not familiar with the Python bytecode spec (to be a little more
> accurate, I'm completely clueless about it), but perhaps something
> similar can be done? Also, another thing to consider is that it
> might be easier to translate python bytecode d
On Thursday 24 July 2003 15:55, Juergen Boemmels wrote:
> Magic: 7f 45 4c 46 01 01 01
00
--
00 00 00 00 00 00 00 00
> OS/ABI:UNIX - System V
Patch is in, please resync and try it.
> boe
Daniel
On 24 Jul 2003, Luke Palmer wrote:
> Klass-Jan Stol writes:
> > module, right? I don't know Python, and I've a little experience
> > with IMC, but it seems to me only a new code generator module should
...[snip]
> Well... sortof. It's definitely going to take writing a whole new
> code generato
Daniel Grunblatt <[EMAIL PROTECTED]> writes:
> On Thursday 24 July 2003 15:14, Simon Glover wrote:
> > On Thu, 24 Jul 2003, Daniel Grunblatt wrote:
> > > I have checked in a first attempt to make parrot generate an executable.
> > >
> > > It works fine on x86 - OpenBSD/linux/FreeBSD and should als
On Thursday 24 July 2003 15:48, Juergen Boemmels wrote:
> Daniel Grunblatt <[EMAIL PROTECTED]> writes:
> > I have checked in a first attempt to make parrot generate an executable.
>
> This is very cool.
Thanks.
>
> > It works fine on x86 - OpenBSD/linux/FreeBSD and should also work on
> > NetBSD
>
On Thursday 24 July 2003 15:14, Simon Glover wrote:
> On Thu, 24 Jul 2003, Daniel Grunblatt wrote:
> > I have checked in a first attempt to make parrot generate an executable.
> >
> > It works fine on x86 - OpenBSD/linux/FreeBSD and should also work on
> > NetBSD
>
> It's not working for me on Lin
Index: exec.c
===
RCS file: /cvs/public/parrot/exec.c,v
retrieving revision 1.1
diff -u -r1.1 exec.c
--- exec.c 24 Jul 2003 17:18:30 - 1.1
+++ exec.c 24 Jul 2003 18:45:22 -
@@ -12,7 +12,9 @@
*/
#include
-#include
+#if HA
--- chromatic <[EMAIL PROTECTED]> wrote:
> On Thursday, July 24, 2003, at 08:49 AM, David Wheeler wrote:
>
> > On Wednesday, July 23, 2003, at 05:57 PM, chromatic wrote:
> >
> >> The first is a deeper question -- besides inheritance, there's
> >> delegation, aggregation, and reimplementation (t
On Thu, 24 Jul 2003, Daniel Grunblatt wrote:
> I have checked in a first attempt to make parrot generate an executable.
>
> It works fine on x86 - OpenBSD/linux/FreeBSD and should also work on NetBSD
It's not working for me on Linux/x86 -- the build is failing with:
In file included from exe
At 10:55 AM 2003-07-24 -0600, Nick Pinckernell wrote, of Pod:
1. IT'S NOT INTUITIVE
IT ISN'T? You can take normal English sentences alternating with
codeblocks, put "=pod" before and =cut after, and it's got a 99% chance of
being good as Pod. That's pretty intuitive, for an intuitively intuit
I have checked in a first attempt to make parrot generate an executable.
It works fine on x86 - OpenBSD/linux/FreeBSD and should also work on NetBSD
For PPC (Darwin) it generates code correctly just for programs that use *only*
fully jitted opcodes.
It should work with or without JIT_CGP.
Afte
-Original Message-
From: chromatic [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 12:56 PM
To: Potozniak, Andrew
Cc: '[EMAIL PROTECTED]'
Subject: Re: passing arguments to tests
On Thursday, July 24, 2003, at 09:46 AM, Potozniak, Andrew wrote:
>> Correct me if I'm wrong but calli
On Thursday, July 24, 2003, at 09:46 AM, Potozniak, Andrew wrote:
Correct me if I'm wrong but calling $self->SUPER::somesub calls a sub
in the
functional context which will not pass the "calling class" along with
it.
Okay, you're wrong. :)
'SUPER::' is just a hint to the method dispatcher to m
Ok, wow, didn't think I'd generate this much feedback.
First of all, let me say that yes, I agree, the perldoc name
for the sourceforge project is bad--I was going to change it.
Second, I was originally thinking about this for Perl 5.
However, after reading some of the Perl 6 RFC's I would want
t
>I'm afraid your code won't work.
As stated below I got it to work with my example :-p
>Okay, you've subclassed a functional module. But this means that
>you'll be >passing the package name as the first argument, not a test
>name. This will generate a "this >test does not exist" warning with
On Thursday, July 24, 2003, at 08:49 AM, David Wheeler wrote:
On Wednesday, July 23, 2003, at 05:57 PM, chromatic wrote:
The first is a deeper question -- besides inheritance, there's
delegation, aggregation, and reimplementation (think mock objects)
that can make two classes have equivalent i
On Thursday, July 24, 2003, at 09:25 AM, Kurt Starsinic wrote:
Sounds like you want Java-style "interfaces" to me.
Follow the thread back. Objective-C had them way first, and their
ur-name is "protocols."
D'oh! Sorry, I had read that, but then forgot.
David
--
David Wheeler
> "David" == David Storrs <[EMAIL PROTECTED]> writes:
David> Other than that, I think (and have always thought) that POD is pretty
David> close to perfect.
I've written 175 magazine articles and my latest best-selling book
in Pod. I rarely find it lacking for typical documentation.
--
Rand
On Wednesday, July 23, 2003, at 05:57 PM, chromatic wrote:
The first is a deeper question -- besides inheritance, there's
delegation, aggregation, and reimplementation (think mock objects)
that can make two classes have equivalent interfaces. I'd like some
way to mark this equivalence *withou
On Wed, Jul 23, 2003 at 10:49:40PM -0600, Nick Pinckernell wrote:
> Hello All,
> My name is Nick Pinckernell.
Hi Nick,
Other people have already commented on most of your points, so I won't
repeat, except to say that I agree that the name "perldoc" is already
taken, and that POD really is pretty
On Wed, Jul 23, 2003 at 10:49:40PM -0600, Nick Pinckernell wrote:
> The idea is: a structured Javadoc style system for Perl. It would be very
> dependant on multiline comments (I've seen the Perl 6 RFC).
>
> I think this idea would be really good for Perl 6, because, in my opinion,
> POD is lacki
Andrew Savige wrote:
Just curious, has anyone had STAF?
http://staf.sourceforge.net/index.php
I ran across STAF when I was researching freeware test harnesses, and I
recommended that my client evaluate both QMtest and STAF (they chose
neither of them, probably because they wanted commercial sup
[EMAIL PROTECTED] (Nick Pinckernell) wrote on Wed, 23 Jul 2003 22:49:40 -0600:
I have just recently taken over the sourceforge project
perldoc. However, currently, there is not much there. It was started
about a year ago, and no work was ever done on the idea by the previous
project owner.
Th
I'm afraid your code won't work.
> package TestHarnessSubClass;
[snip]
> #This creates TestHarnessSubClass into a sub class of Test::Harness
> use base "Test::Harness";
[snip]
> sub runtests{
> my $self = shift;
[snip]
> $self->SUPER::runtests(@_);
> }
Okay, you've subclassed a functional mo
This is a real simple example of what you can do for sub classing. Object
oriented design is a wonderful thing :-D
TEST HARNESS SUB CLASS (TestHarnessSubClass.pm)##
#!/usr/local/bin/perl
package TestHarnessSubClass;
use warnings;
use strict;
#This creates TestHarnessSubClass
Simon Glover <[EMAIL PROTECTED]> writes:
> Test number 6 in io.t is failing on a number of the tinderboxes with
> a double-free error.
>
> Test 6 does this:
>
> open P0, "temp.file", "<"
> clone P1, P0
> read S0, P1, 1024
> print S0
> end
>
> And the clone function in th
Benjamin Goldberg <[EMAIL PROTECTED]> writes:
> Lars Balker Rasmussen wrote:
>> However, now the 4th test fails on Solaris (and most likely other OS's
>> witout setenv/unsetenv). This is because the test relies on a key
>> disappearing from %ENV when it's been unsetenv'ed - this doesn't
>> happen
to link with python, we should probably write our own parser.[1]
Just use Perl 6 to write it :). Ooops... looks like a chicken-and-egg
problem...
Greetings,
Christian
- Original Message -
From: "Luke Palmer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, July 24, 2003 2:22 AM
Subject: Re: approaching python
> Klass-Jan Stol writes:
> > > The thing is, I don't have a lot of experience when it co
Luke Palmer <[EMAIL PROTECTED]> writes:
> Iain Truskett wrote:
>> * Nick Pinckernell ([EMAIL PROTECTED]) [24 Jul 2003 14:50]:
>>
>> [...]
>> > The idea is: a structured Javadoc style system for Perl. It would be
>> > very dependant on multiline comments (I've seen the Perl 6 RFC).
>>
>> Why so?
>
Klass-Jan Stol writes:
> > The thing is, I don't have a lot of experience when it comes to
> > compilers, but I do know a whole lot about python. :) If this
> > approach makes sense, is there someone with IMCC experience who'd
> > be willing to do some virtual pair programming with me and spike
> >
- Original Message -
From: "Michal Wallace" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 23, 2003 4:48 PM
Subject: approaching python
>
> Hey all,
>
> I've been thinking about the "compiling python to
> parrot" concept. Right now it looks like the
> approach is to st
From: Dan Sugalski [mailto:[EMAIL PROTECTED]
> We are going to do all I/O under the hood asynchronously.
> Completed async IO puts an event in the event queue...
I am new to parrot, but I've had plenty of experience with (non-unix)
I/O systems. Having a totally async core in Parrot is pretty clea
Iain Truskett wrote:
> * Nick Pinckernell ([EMAIL PROTECTED]) [24 Jul 2003 14:50]:
>
> [...]
> > The idea is: a structured Javadoc style system for Perl. It would be
> > very dependant on multiline comments (I've seen the Perl 6 RFC).
>
> Why so?
>
> > I think this idea would be really good for
50 matches
Mail list logo
