Rather than adding another file, I'd recommend putting these under
DESIGN in docs/ROADMAP. Then they're all in one place for Chip when
he gets more tuits.
I added a link to this one there.
Regards.
On Jul 25, 2005, at 10:53 AM, Leopold Toetsch wrote:
Nicholas Clark wrote:
This all g
Nicholas Clark wrote:
This all got Warnocked, didn't it?
Having read it twice, I don't think I'm going to get closer to a decent
response than "er, this is really a call for the designer to make, isn't it?"
Mway be it's time to start a WARNOCKED file in parrot's root dir and
collect such und
On Mon, Apr 18, 2005 at 12:15:34PM +0200, Leopold Toetsch wrote:
> Below is some stuff, which I'm unsure of how it should be implemented
> eventually. Input is highly welcome.
> TODO items and design issues
>
> 1) bitwise or, and, xor
>
> We currently have two distinct sets of opcodes and MMD
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> TODO items and design issues
And some more:
6) stringish MMD infix operators: concatenate, repeat
The implementation takes either two strings, or one string and an integer
repeat count. Again not much multi to dispatch IMHO.
Missing: PMC variants of
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> 5) new opcodes that return a new result:
> Px = n_add Py, Pz # new Px created
> These opcodes will be done RSN.
RSN is now. There is one basic test in t/pmc/integer.t. Overloading
is tested in mmd.t.
More tests are welcome for other PMCs.
Cav
Below is some stuff, which I'm unsure of how it should be implemented
eventually. Input is highly welcome.
Thanks,
leo
TODO items and design issues
1) bitwise or, and, xor
We currently have two distinct sets of opcodes and MMD functions for
numeric (i.e. integer) and string bitwise functionalit
