Oh, sorry... Larry Wall didn't actually to Phoenix-pm. At least not that
I know of. This was a forward from me. Thought ya'll might find this
interesting... on a Perl 5 level, in a Perl 6 sort of way, and also on
the subject of software refactoring.
-scott
On 0, Larry Wall [EMAIL PROTECTED]
Hi Peter,
There are several source filters that make select changes and modules
that give select Perl 6 features to Perl 5. All in all, there's a
lot there -- I've written Perl6::Contexts, for example, which diddles
the bytecode to give Perl 5 programs most of the new contexts from
Perl 6. In
See also http://use.perl.org/~LTjake/journal/23570 =)
-scott
On 0, Stevan Little [EMAIL PROTECTED] wrote:
Autrijus,
While I like the current Pugs banner, it's basically a variation of the
Hugs banner. So I put my years of art school training to work, and some
help from FIGlet I created
Hi Autrijus,
(Resend, this time cc'ing perl6-compilers with the correct address.)
[EMAIL PROTECTED] is having problems right now... the spammers are winning.
Hey Scott. I have yet to read your Perl 6 Now! book (a friend will
bring it to Taiwan next month), but I've just discovered the
On 0, Juerd [EMAIL PROTECTED] wrote:
However, is the name boolean final? I would prefer true, perhaps
with a corresponding false.
I want an okay. Routines should be able to return okay to indicate
an ambivalent degree of success. okay would be defined as true | false,
so:
some_routine()
Since this horse came back to life, I'm going to give it a good thrashing, and
I've got goons to help me.
I've asked the Phoenix Perl Mongers for their take on the situation. I've posted
a _completely_ unbiased synopsis of the situation. Here are excerpts from the replies:
Tony's take:
Rename
Let me summerize my undestanding of this (if my bozo bit isn't already
irrevocably set):
* %hashfoo retains the features of P5 $hash{foo} but does nothing to counter the
damage of removal of barewords
* %hash`foo occupies an important nitch, trading features (slice, autovivication)
to optmize
of other people I hope you really enjoy being offended.
Na na na! One of these days I'm going to resolve to hunt you down to irritate you
as you do to me.
-scott
On 0, chromatic [EMAIL PROTECTED] wrote:
On Thu, 2004-04-15 at 12:27, Scott Walters wrote:
Without commenting on the rest
Ack - well, I was downright antagonistic, so I really earned it.
I can only try to accept criticism as well as the rest of the list has.
Apology accepted of course, and an apology of my own to the list who had to
suffer me and chromatic who didn't take me too seriously ;)
-scott
On 0,
When I announced that I fixed a version of Perl6::Variables to do ,
crickets chirped. I dislike having to place a lot of matching quotes,
brackets, parenthesis, and braces in my code. You must stop and
visually inspect code to make sure it balances out and even then is a
common source of bug
Juerd,
You'd do well to not remove the conclusion of my post when the conclusion
is that the I strongly support you. Otherwise, your reply, read out of
context, sounds like you're fending off an attacker ;)
People would do well to seperate the merits of the idea from the merits of the
suggested
I propose we pretend that $$foo = 'bar' stills work and use that as a benchmark
for hash subscripting ease. If it requires fewer keystrokes or neuron fires to
write Perl 4 code, then Perl 6 might be succeding on the programming in the
small but failing at programming in the large.
${'bar'} =
What is a list reference?
What is an array?
...
What is a list?
Hi Juerd,
There was a thread on this not long ago. I forgot it's name.
Apo 2 said:
[1,2,3]
is syntactic sugar for something like:
scalar(list(1,2,3))
... suggesting that lists could have references taken to them, much
I've updated Damian's Perl6::Variables module to treat %foo{bar} as %foo{bar()}
and to handle %foobar and %foobar baz. If this syntax is finalized, I'll
send Damian a patch.
This is at:
http://www.cpan.org/modules/by-authors/id/S/SW/SWALTERS/Perl6-Variables-0.02_001.tar.gz
still doesn't handle %foo{'bar'}baz.
Thanks,
-scott
On 0, Scott Walters [EMAIL PROTECTED] wrote:
I've updated Damian's Perl6::Variables module to treat %foo{bar} as %foo{bar()}
and to handle %foobar and %foobar baz. If this syntax is finalized, I'll
send Damian a patch
On 0, Rod Adams [EMAIL PROTECTED] wrote:
Also, isn't it a pain to type all these characters when they are not on
your keyboard? As a predominately Win2k/XP user in the US, I see all
these glyphs just fine,but having to remember Alt+0171 for a « is going
to get old fast... I much sooner
Hi kids,
I have work-related reason to add a B backend for Perl 5 to the perl6
compiler. I'm looking at creating an assembler for Perl 5's B bytecode
along the lines of IMCC, and creating patches against languages/perl6/IMCC.pm
and languages/perl6/IMCC/* to conditionally, using some sort of
Mike,
Part of the beauty of PMCs is that you can have very compact
storage given a dedicated eg int array type. Generating these
would not be a bad thing. The typical case still remains, that
arrays will contained mixtures of all datatypes.
On Wed, 24 Jul 2002, Mike Lambert wrote:
This patch
Mike,
Was very happy to see your message. People don't often agree with
me. I'm not very agreeable.
On Thu, 25 Jul 2002, Mike Lambert wrote:
Scott Walters wrote:
Part of the beauty of PMCs is that you can have very compact
storage given a dedicated eg int array type. Generating
On Wed, 24 Jul 2002, Mike Lambert wrote:
Mike,
I submit some patches a few days back, one with updates to the documentation
from my reverse engineering and probing efforts. I also implemented a patch
to make Array.PMC handle keys recursively. I'm kind of testing the waters
here. If they are
When a KEY * key datastructure is passed to a keyed method in array.pmc,
and key-next is true...:
array.pmc will recurse into the keyed lookup method of the PMC that it
contains, passing it key-next.
This implements the recursive indexing behavior as described in PDD08.
-scott
Index:
On Mon, 22 Jul 2002, Angel Faus wrote:
In my opinion, there are actually two different things to dicuss:
- keyed opcodes
- keyed methods on the PMC vtable
...
Keyed opcodes can stay in the interest of code density.
No. Keyed access for all methods stays. You're forgetting one
On Mon, 22 Jul 2002, Nicholas Clark wrote:
I will now demonstrate my ignorance of the parrot build system:
Do pmc files get turned pretty directly into C code?
Yes, via classes/pmc2c.pl. I don't see any code in there to replace the
// style comments, but I didn't read too carefully.
Dan,
As it stands, KEY * is a win when:
1) All of the array indices are constants and hardcoded into the instruction
stream
2) The PMC handling the index does not have to recurse.
In all other cases, as it currently stands, it is a loose. I hate to come out
and be so blunt, but I
Dan,
Thanks for being a good sport. I'm not in a hurry here - don't feel like you
need to be.
I propose that keyed access do exactly eight things:
* fetch a PMC using a key
* fetch a integer using a key
* fetch a number using a key
* fetch a string using a key
* store PMC
Btw, to the best of the ability of my backscroll, I'm trying to archive useful
conversations on http://www.slowass.net/wiki/?ParrotVirtualMachine. If I miss
something, feel free to add it.
-scott
On Sun, 14 Jul 2002, Dan Sugalski wrote:
At 10:09 AM +0100 7/14/02, Simon Wistow wrote:
On
Still trying to solve the assembly/PMC vector interface. Accosted Dan on IRC re:
multidimentional indices.
Looking for thoughts on this.
Working under assumptions:
* There is no assembler syntax yet, or atleast not final.
* Hardcoding KEY *'s into the assembly is the only way so far.
*
Melvin co,
Which IRC network, which channel?
Sorry for past, present, and future newbie questions. Doubly so for having
overlooked documentation. Docs are in excellent condition, considering.
Since I can't help but to pipe up, I should disclaim myself: Parrot is
extremely coo. The core team
28 matches
Mail list logo
