>) could all
> $string.rtrim internally.
>
If I were going to have ltrim() and rtrim(), I'd implement them in terms of
trim() rather than the other way around.
-Scott
--
Jonathan Scott Duff
perlpi...@gmail.com
ttached a diff if anyone is interested.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
? diff.jsd
? diff.duff
Index: assemble.pl
===
RCS file: /home/perlcvs/parrot/assemble.pl,v
retrieving revision 1.24
diff -u -r1.24 assemble.pl
--- assemble.
On Tue, Dec 04, 2001 at 04:11:58PM -0500, Dan Sugalski wrote:
> Seriously, there are real answers to a whole lot of design questions. Ask
> 'em and I'll get FAQable answers to 'em once and for all.
Could the FAQ be made a wiki so that others can play too?
-Scott
--
Jonat
;s time to work on nothing
but Parrot? If so, how?
And for my own personal edification, has anyone tried to work a deal
(through YAS perhaps) for Parrot like Damian Conway has for Perl?
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
ale specific
representation?
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On Fri, Jan 25, 2002 at 01:56:20PM -0500, Bryan C. Warnock wrote:
[ rather interesting ramble about people, Perl, and personality ]
Someone needs to add this stuff to http://dev.perl.org/perl6/people
or perhaps start a Perl6-personality guidebook :-)
-Scott
--
Jonathan Scott Duff
[EMAIL
at in order for Perl 6 programs to be written in
Unicode, Parrot needs to grok unicode (everwhere, including regular
expressions).
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
sional hyper cube of a Karnaugh map.
Yep, that's the one. I remember implementing the algorithm long ago
as part of a computer architecture class I was taking. I don't think
I have the code where I can get it, but it'd probably be best to
reimplement from scratch anyway.
-Scott
--
I'm fiddling around with parrot and created a getopt macro (inspired by
the arg processing in Leon Brocard's uniq.pasm :-). This is my first
attempt at something semi-useful in parrot.
Anyway, here it is and looking for comments,
-Scott
>8>8 >8 >8-
# getopt.macro
#
# Scans
an create tools to deal with it (uuencode anyone?). Also by not keeping
to 80 columns, we can weed out the modern tools that still have such
limitations and encourage the authors to fix them. And if *that* turns
out to be too big of an endeavour, we can always go back to 80 columns,
but I'm guessing whatever problems there are will be small and
localized.
just my humble opinion,
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
obj.$bar() # a method variable
The same could be used for ordinary subroutines:
.local string mysub
mysub = "foo"
$mysub()# calls the foo subroutine
-Scott
--
Jonathan Scott Duff <[EMAIL PROTECTED]>
// DO NOT EDIT THIS FILE - it is machine generated -*- c++ -*-
So, perhaps it's not the .h files we should be parsing, but whatever source
files were used to generate them. Though, of course, some C++-to-Perl6 tool
would be a good thing too. :-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
# New Ticket Created by "Jonathan Scott Duff"
# Please include the string: [perl #51838]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=51838 >
---
osname= cygwin
osvers= 1.5.24(0.15642)
arch= cygwin-threa
Is there some reason that runtime/parrot/library isn't in the list of
search paths for both include_paths and dynext_paths?
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
Here's a patch to implement the split opcode such that it splits on
strings rather than regular expressions. I've also added a test to
t/op/string.t
Files affected:
M ops/string.ops
M t/op/string.t
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
=== ops/
ion of the "property" (just reusing the name from
subversion) names is up to whoever generates/consumes them, so they
could be anything
#language perl
#version 6
#file hello.p6
#line 1
#source say "hello world\n";
#chapter 4
#verse 7
#scoundrel Bill Sikes
... PIR that implements the HLL ...
etc.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
you are generating may be
large (like say, between a very complex and rich language like Perl6 and
a much simpler language like PIR ;). TGE lets you factor out the
complexity of your source language in incremental steps (as small or as
large steps as you want).
> Good luck for today's presentation :)
Yeah, good luck Pm :)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
TECTED]
>
> In the future, if you want to submit an RFC mail it to
> [EMAIL PROTECTED] only.
http://tmtowtdi.perl.org/rfc/meta/ says that you should send your RFCs to
[EMAIL PROTECTED] rather than [EMAIL PROTECTED]
Thanks for getting the RFC repository up an running Nat.
-Scott
--
nstruct and that got me thinking about python's
docstrings. It would be neat to have something similar in perl.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
ll Perl platforms
> on the UNIX epoch".
>
> Sound better?
Yep. Or more generally "Standardize Perl on all platforms to one
common time epoch" and reccommend the Unix epoch since it's so
widespread. :-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
ount on it. But that won't be our fault as much as
Unix's :-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
llions* of Jews for whom "0 AD"
is meaningless. s/Jews//
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
n a float and *bam* you've got <1 second precision as far
as your floats or doubles can carry you.
> But make the core language easily accessible to everyone.
Funny, that's the exact argument I would use *against* mjdate().
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
MES
@foo = split; pop @foo until $foo[-1];
@foo = split ' ';
# BECOMES
@foo = split /\s+/; shift @foo;
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On Sat, Oct 07, 2000 at 10:38:21AM +0200, Bart Lateur wrote:
> On Fri, 6 Oct 2000 23:26:44 -0500, Jonathan Scott Duff wrote:
>
> > @foo = split;
> > # BECOMES
> > @foo = split; pop @foo until $foo[-1];
>
> That doesn't fly. What if that last field
25 matches
Mail list logo
