In article <[EMAIL PROTECTED]>, brian d foy
<[EMAIL PROTECTED]> wrote:
> There are other things to consider, and to me it looks like this design
> decision isn't based on what's easier for the Perl 6 programmer but
> what's easier for the implementors.
My comment here was offensive to Damian (and
Fixed in r19073.
--
Matt Diephouse
Here's a fun algorithm for you. How do you find a substring within another
string?
I really want to apply something like this patch. I'd like to take advantage
of libc functions to do the hard work, rather than walking through a string,
byte by byte. Unfortunately, libc functions think \0 ma
On Fri Apr 13 06:15:19 2007, infinoid wrote:
> On Mon Apr 03 20:43:53 2006, petdance wrote:
> > The lint target needs to be renamed to splint.
> >
> > Then create a new lint target to support Sun Studio.
> >
> > And update the tags target.
>
> As of today's date (2007-04-13), it appears that all
Am Samstag, den 16.06.2007, 14:00 -0700 schrieb chromatic via RT:
> I fiddled with this patch and test a bit, but I get the error:
>
> 1..5
> Seek down worked
> seek failed (32bit)
> current instr.: 'test_io_mmap' pc 61 (t/op/io_mmap.t:44)
> called from Sub 'main' pc 38 (t
Hi,
GDR! wrote:
I'm new here so I'll say hello - I'm GDR!.
Welcome! :-)
I was looking at the Parrot project recently and I'd like to
implement the VM in hardware. I'm not deeply into the project,
however, so I'd like to ask you if the Parrot bytecode is now stable
enough to begin hard
On Sunday 17 June 2007 11:21:22 Ron Blaschke wrote:
> Attached patch should take care of tickets #37301 and #40972.
Thanks, applied as r19068.
-- c
brian wrote:
[writing publicly to head off any notions there's a personality problem
here]
I said I wasn't going to continue this discussion, and I'm not. But I
do want to agree publicly that there's no clash between brian and
myself. I have only the highest respect for brian: as a person, as
On Sun, 17 Jun 2007 01:41:30 -0500
Andy Lester <[EMAIL PROTECTED]> wrote:
> I cringe at functions where the behavior is dependent on parms
> passed in. In the case of Parrot_get_runtime_prefix, if you call it
> as Parrot_get_runtime_prefix(&str) then str is populated, or if you
> call Parrot_get_
# New Ticket Created by Ron Blaschke
# Please include the string: [perl #43235]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43235 >
Attached patch should take care of tickets #37301 and #40972.
Windows XP - Visual C++ 8
In article <[EMAIL PROTECTED]>, Damian Conway
<[EMAIL PROTECTED]> wrote:
[writing publicly to head off any notions there's a personality problem
here]
> brian wrote:
> > I know you think it's easier to teach and explain, but that's because
> > you came up with it.
>
> I hope I'm not that shal
# New Ticket Created by Ron Blaschke
# Please include the string: [perl #43234]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43234 >
Windows XP
Visual C++ 8
Parrot r19058
Remove C<-DNDEBUG> from CFLAGS, i.e. compile Parr
After much help from Ron Blaschke to get this working nicely on Win32,
I've applied the latest patch as r19059 and am now closing the ticket.
Paul
Paul Cochrane wrote:
>> Paul Cochrane wrote:
>> >> Without the manual setting of PATH before building?
>> >
>> > With the manual PATH setting. There are several tickets for cygwin
>> > not building in RT; are they all related? Is there something like a
>> > hints file where the information about
Paul Cochrane wrote:
> I couldn't get your patch to apply cleanly and so hacked it in by
> hand. I'm attaching a new patch to this email (which is quite
> possibly identical to yours) so that you can give it a quick test. If
> all is happy, then I'll commit the change and close the ticket.
I lo
* Damian Conway ([EMAIL PROTECTED]) [070616 23:21]:
> I will, however, take a moment to answer the accusation that I appear to
> have redesigned Pod the way I did in order to make implementation
> easier...
The opposit: your work is known to seek the corners of the language
which hurt most. So pl
* Jonathan Scott Duff ([EMAIL PROTECTED]) [070616 20:15]:
> You mention OOP. For Perl 5 we have a standard, if very general,
> syntax and "open" semantics that have allowed people to implement OOP
> in a variety of ways. This was all well and good for a while until we
> realized that there should
17 matches
Mail list logo
