. - but it doesn't necessarily matter whether it's
SPARC-based or not.
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
? (To prevent
the aforementioned bit-shifting of WTF strings.)
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
operations,
but I think that makes my head hurt so I'm not going there righ tnow)
Good 'nuff. Thanks,
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
out what a string is yet?
[1] And by we, I mean you[2].
[2] And by you, I mean you plural.
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
{snipped, obviously}
Hmmm... very good.
One question.
Does (that which the masses normally refer to as) binary data
fall inside or outside the scope of a string?
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
we'll see how well that one works.
I don't understand. Substitute grapheme for character, as you're
staying away from glyphs, but getglyph for getcharacter?
And what about codepoints that *are* glyphs and/but aren't graphemes?
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
On Mon, 2004-04-26 at 08:12, Dan Sugalski wrote:
At 9:34 PM -0400 4/25/04, Bryan C. Warnock wrote:
On Sun, 2004-04-25 at 16:34, Dan Sugalski wrote:
Just a heads up, there are two things that have been pointed out.
First, the transset op is transcharset. The abbreviation was a bit sloppy
On Thu, 2004-04-22 at 12:18, Jeff Clites wrote:
Unicode is an actively evolving standard. It's far from legacy.
On Thu, 2004-04-22 at 15:07, George R wrote:
I don't agree with the Unicode legacy comment... :-(
Creating tomorrow's legacy today. :-)
--
Bryan C. Warnock
bwarnock
# New Ticket Created by Bryan C. Warnock
# Please include the string: [perl #28383]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=28383
The email address of record has only been defunct for a year and a half
On Thu, 2004-04-08 at 21:14, Robert Spier wrote:
b) Is it kosher/proper to update email references in it?
Sure.
Disagreement. This makes it harder to find relevant email messages in
the archives.
Excellent point.
(Ignore that section of my previously posted patch.)
--
Bryan C
a) Is the ChangeLog autogenned?
b) Is it kosher/proper to update email references in it?
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
Has it been two years already?
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
On Tue, 2003-06-03 at 03:54, Henrik Tougaard wrote:
On Sat, May 31, 2003 at 09:54:45AM -0400, Bryan C. Warnock wrote:
[snip]
Part of what was snipped was this line:
(For the sake of using real numbers, I'll assume 32/64.)
Currently, the flow is, in variable sizes:
Opcodes: 32
On Sat, 2003-05-31 at 09:57, Bryan C. Warnock wrote:
On Sat, 2003-05-31 at 09:53, Leopold Toetsch wrote:
Bryan C. Warnock [EMAIL PROTECTED] wrote:
As mentioned previously. Makes IMCC and PASM constant keywords
consistent, with '.const'.
As mentioned previously ;-) this doesn't
On Sun, 2003-06-01 at 10:08, Gopal V wrote:
If memory serves me right, Bryan C. Warnock wrote:
No .. to add large numbers very quickly ... ie split registers and
enemies ;-)
Understood. My point was that - to parallel virtual machines with
physical ones - the big drive for 64-bit
?
It doesn't look that way, from the direction that PMCs have gone.
Can we simplify interpreter types this much, while still providing
extended numerics to hosted languages?
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
On Sat, 2003-05-31 at 09:53, Leopold Toetsch wrote:
Bryan C. Warnock [EMAIL PROTECTED] wrote:
As mentioned previously. Makes IMCC and PASM constant keywords
consistent, with '.const'.
As mentioned previously ;-) this doesn't work that simple. Imcc already
has:
.const type ID
On Sat, 2003-05-31 at 11:15, Gopal V wrote:
If memory serves me right, Bryan C. Warnock wrote:
Not to mention all the *other* problems we'll have if we've got more
than 2^31 different opcodes. (Although that's why there's UUIDs now,
isn't there?)
I think parrot has already crossed
On Sat, 2003-05-31 at 11:43, Leopold Toetsch wrote:
Bryan C. Warnock [EMAIL PROTECTED] wrote:
The flow *really* is, in value sizes:
Opcodes: 32 (constants are limited by the spec)
In which spec? How would we handle 64 bit INTVAL constants on 32 bit
systems?
Parrotbyte.pod
.
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
# New Ticket Created by Bryan C. Warnock
# Please include the string: [perl #22386]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=22386
As mentioned previously. Makes IMCC and PASM constant keywords
consistent
Parrot in some sort of production
mode and schlepping around old PBC files, a standalone format converter
would be a nice add-on. Perhaps even based on the add-on Perl-based PBC
thingy above.
It's way to early to get wrapped up in Parrot's own legacy.
--
Bryan C. Warnock
bwarnock@(gtemail.net
On Wed, 2003-05-28 at 11:13, Clinton A. Pierce wrote:
Is there is reason not to s/\.constant/.const/g for consistency's sake?
And actually, on further consideration, .const isn't what I want
either.
Which doesn't invalidate my question. :-)
--
Bryan C. Warnock
bwarnock@(gtemail.net
that (IMCC
has .const) so I'm all set now.
Is there is reason not to s/\.constant/.const/g for consistency's sake?
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
]/msg06918.html
[3] Or, how well it does what it should do. I don't think anyone's
really addressed how much work to commit to such a thing.
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
extended, and require at least 10 bytes. (Which, coincidentally, is the
size of the x86 fp registers.)
In memory, they're padded to 12 or 16 bytes to preserve word boundaries.
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
solution,
but I doesn't mean that I have to like it.
Let me dig through my notes.
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
, but people don't really
use that for stringification.
(BTW, direct mail to you, from me, never gets through. Times out.)
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
the
rule set small, simple, and consistent.
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
on the weekly
discussions, just report on what you've released. Much like the old
sub-lists would step away to discuss some particular topic head-to-toe,
p6d should discuss every topic toe-to-toe. It'll evolve, but until
then, there'll be the occasional nudge. :-)
--
Bryan C. Warnock
bwarnock
On Thu, 2002-11-28 at 18:47, Bryan C. Warnock wrote:
Yes, but the first digit is 0. Or, more accurately, 0 * 16**2.
Hmmph. Some accuracy. 0 * 16**1
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
, semantics, implementation impacts, ideological
ax grinding, etc. so that p6l can refer people to the old arguments instead
of wasting ever more time on them.
Yeah, I wanted the same thing with PDD 0. :-) Hopefully this will turn
out better. :-)
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
extrapolate.
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
they're closer to the action.
It might help the Parrot people if they knew what their target languages
wanted. (Not that they can guarantee delivery of said requests, of
course. :-)
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
, '.',
but cannot use exponential notation ('e')
- can't have runtime radix, e.g. 2**8#10, because # binds tighter.
- can't say (2**8)#10, because not a literal.
The examples are good and extrapolate nicely, but has the grammar been
defined somewhere (in one form or another)?
--
Bryan C
into Perl6 OO, but we may need
to request some preliminary decisions before then, because the
implications are substantial.
and again...
Let's open these for discussion. Questions/proposals/issues, anyone?
and again... what's the scope of p6d, and how does it differ from p6l?
--
Bryan C
On Mon, 2002-11-25 at 20:00, Joseph F. Ryan wrote:
I agree; perhaps before the argument begins, we should have something to
argue over? :) (i.e., a first draft of these sections)
Sure. On perl6-language. :-)
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
On Mon, 2002-11-25 at 11:04, Nicholas Clark wrote:
Is there any speed advantage in truncating by casting via a C type
[eg a = (int)(short) b]
rather than and on a bitmask
[eg a = b 0x]
?
We're going to have to do that latter to make it work on Crays anyway
Why?
--
Bryan C. Warnock
elsewhere, and b) producing its own documentation, the occasional call
to action and a list of what new and updated docs have been released -
or the occasional reminder of where to find the new and updated docs -
should be sufficient.
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
don't know? :-)
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
(possibly unicode) strings instead of
interpolating characters, as in C\x{1}\x{2}\x{3}\x{4}. The leading
Cv may be omitted if there are more than two ordinals, so C1.2.3
is parsed the same as Cv1.2.3.
See numerical comment above about the implied radix.
--
Bryan C. Warnock
bwarnock@(gtemail.net
On Mon, 2002-11-18 at 10:08, Erik Steven Harrison wrote:
--
On 17 Nov 2002 11:09:53 -050
Bryan C. Warnock wrote:
On Wed, 2002-11-13 at 13:26, Angel Faus wrote:
There are many ways to specify literal numeric values in perl, but
they default to base 10 for input and output. Once
means, justify core functionality to
do so.
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
On Wed, 2002-11-13 at 14:08, Jonathan Scott Duff wrote:
On Wed, Nov 13, 2002 at 07:26:06PM +0100, Angel Faus wrote:
For example:
my $x = 18;
my $y = -18;
my $z = -256:234.254; # negative number
my $e = 256:-234.254; # error
Why?
--
Bryan C
On Mon, 2002-10-28 at 14:41, Larry Wall wrote:
And maybe:
A bitwise operator is just a logic operator scoped to a set of bits.
Hypo-operators. :-)
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
-R (pondering his next move in the unending war against spam)
Nukes.
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
values will be. But you can convert to BigInt at 32 bits
vice 64. (Assuming that's still the plan.)
[1] In My Humble And Oft-Stated But Rarely Patching Opinion ;)
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
targeting a middle ground for C? (Enough to be able to
parse and handle structs natively, and possibly even make calls
natively?)
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
a noticeable ongoing conversation between multiple
people.
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
'.
Are you satisfied enough for me to install it now?
Please? Pretty please? [y]
(Or, in the instance of [n]s, Okay, you can always (test|install) it
later by running $command.)
Beyond that, I like this glimpse of the future.
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
is *too* big (for the heirarchical vtable)
3) Ops that can't/won't fit are done as a sub call, right?
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
to match one thing and one thing
only. Whether that will be an issue with variable-width characters in a
class is largely going to rely on the semantics that are dictated.
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
.
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
, even when you need to.
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
../t/op/hacks.t
../t/op/interp.t
../t/op/gc.t
../t/op/trans.t
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
I won't get to.)
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
Index: byteorder.dev
===
RCS file: /cvs/public/parrot/docs/dev/byteorder.dev,v
retrieving revision 1.1
diff -u -r1.1 byteorder.dev
--- byteorder.dev 19 Jul 2002 02
How does one patch a file to delete?
docs/a5_draft.html can go away now, thank you for playing.
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
www.parrotcode.org/docs seems to like them, so here they are.
This rolls in the byteorder.dev patch previously submitted.
(I see in the patch that we're not consistent with what a line ending
should be. I've left that alone.)
--
Bryan C. Warnock
bwarnock(gtemail.net|raba.com)
Index
an acknowledgment of its
existence. This leaves you wondering if your problem is unimportant or
previously addressed, if everyone's waiting on someone else to answer
you, or if maybe your mail never actually made it to anyone else in
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
On Sun, 2002-08-18 at 18:53, Brent Dax wrote:
# And do we need a RFC like definition of should/may/must/mustn't?
If so, I'd suggest the definition be patched into PDD0, so it's shared
by all PDDs instead of repeating the definitions everywhere.
Noted.
--
Bryan C. Warnock
bwarnock
. :-)
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
be coroutines
4) We want to be fast
Is there (as I don't know) anything else in Perl (Parrot?) that is
implemented in terms of coroutines or continuations? Or is the only
functional programming support being provided strictly at the language
level?
--
Bryan C. Warnock
bwarnock(gtemail.net
read this, I thought, Well,
duh! If C++ is a requirement, then anyone wanting to interact with ICU
will have a C++ compiler. If they didn't have one, they wouldn't use
it.
Or do you mean that ICU simply hasn't been approached (often) to provide
a C-only implementation?
--
Bryan C. Warnock
bwarnock
, he said, What? We're going to have
code with an alpha channel? :-)
--
Bryan C. Warnock
bwarnock(gtemail.net|capita.com)
, and not for general opcode
use.)
--
Bryan C. Warnock
bwarnock(gtemail.net|capita.com)
as INTVAL in that case.
--
Bryan C. Warnock
bwarnock(gtemail.net|capita.com)
can
shoot it to me and I'll try to integrate, and credit you of course;
otherwise, I'm going to keep moving forward I hope.
I'll post non-code first. (I've legal issues that haven't been hammered
out yet.
--
Bryan C. Warnock
bwarnock(gtemail.net|capita.com)
for some interesting discussion,
especially given Leon Brocard's JVM experimentation.
The PBC metadata should indicate the source language and compiler, for
sure.
--
Bryan C. Warnock
bwarnock(gtemail.net|capita.com)
On Mon, 2002-04-29 at 11:04, Ilya Martynov wrote:
{snip}
Has this question and patch been addressed?
--
Bryan C. Warnock
bwarnock(gtemail.net|capita.com)
the cruft that's accumulated since
the beginning of the current sub is the responsibility of other code.
I'll take this opportunity to repoint to a thread we had last September
in re sub and method prototyping.
The thread starts here:
http:[EMAIL PROTECTED]/msg08182.html
--
Bryan C. Warnock
, and
returns that. If that fails, it gives up.
I thought the point of the discussion was turning off the GC until such time
that it was ready to go. I know what it *does* - what should it *do*?
{Rest of the comments snipped.}
--
Bryan C. Warnock
[EMAIL PROTECTED]
the system.) Going back and
DOD/GC may then give you enough room to finish initialization, but probably
not enough to do anything useful, so I don't see that as a reason to run GC
then, either.
--
Bryan C. Warnock
[EMAIL PROTECTED]
/bootstrapping process can trigger a GC run to free up as much
memory as it can. The remainder of the interpreter can then start up,
running through the GC.
--
Bryan C. Warnock
[EMAIL PROTECTED]
have been applied recently.)
Did I sneak one in somewhere else that I can't find?
--
Bryan C. Warnock
[EMAIL PROTECTED]
strings, I'd say hide it, and we'd slap it in as part of
Parrot's string libs. But I don't think we can abstract that far.
--
Bryan C. Warnock
[EMAIL PROTECTED]
not representing the actual allocation size (which
it looks like Mike Lambert's roll-up patch does) so we have the option of
shipping 0.0.5 out the door, and then we'll address the larger questions
later.
--
Bryan C. Warnock
[EMAIL PROTECTED]
the current ones?
--
Bryan C. Warnock
[EMAIL PROTECTED]
these levels of
indirection confuses me to no end as to what's inside and what's not.
--
Bryan C. Warnock
[EMAIL PROTECTED]
C. Warnock
[EMAIL PROTECTED]
On Tuesday 02 April 2002 01:48, Josh Wilmes wrote:
(apparently the enum type is signed by default).
Implementation defined.
--
Bryan C. Warnock
[EMAIL PROTECTED]
. Again, it's probably best to bury this within the alloc calls
themselves, so that the algorithm is best encapsulated.
Thoughts?
--
Bryan C. Warnock
[EMAIL PROTECTED]
( ;boundary)
ten-- save ( ;boundary)
eleven--saved (endproc)
--
Bryan C. Warnock
[EMAIL PROTECTED]
On Friday 22 March 2002 09:37, Joshua Nye wrote:
Works ok up to 15 items on the stack. After that I get screwy results back.
Is that with or without my patch?
http:[EMAIL PROTECTED]/msg09093.html
--
Bryan C. Warnock
[EMAIL PROTECTED]
];
- }
+for (j=0; j1000; j++) {
+k += a[j][i];
+}
}
This all boils down to: keep things near to each other that get
--
Bryan C. Warnock
[EMAIL PROTECTED]
We're still all over the place with typedef name formats. We've FOO, Foo,
and foo_t. We tried to hash this out before, but we didn't come to a clear
consensus. (We got sidetracked by typedeffing pointers to typedefs.)
What's it going to be?
--
Bryan C. Warnock
[EMAIL PROTECTED]
on top of stack!
--
Bryan C. Warnock
[EMAIL PROTECTED]
On Friday 22 March 2002 10:07, Brent Dax wrote:
Bryan C. Warnock:
# We're still all over the place with typedef name formats.
# We've FOO, Foo,
# and foo_t. We tried to hash this out before, but we didn't
# come to a clear
# consensus. (We got sidetracked by typedeffing pointers
)
eleven--saved (endproc)
Str eleven
Str ten
Str nine
Str eight
Str seven
Str six
Str five
Str four
Str three
Str two
Str one
--
Bryan C. Warnock
[EMAIL PROTECTED]
. (function pointers, enums, simple type pointers,
etc.), and would just assume change *everything* from FOO to something else.
Although I'd be happy with leaving the big four in all caps.
--
Bryan C. Warnock
[EMAIL PROTECTED]
. ;-)
--
Bryan C. Warnock
[EMAIL PROTECTED]
On Friday 22 March 2002 11:36, Dan Sugalski wrote:
At 10:02 AM -0500 3/22/02, Bryan C. Warnock wrote:
We're still all over the place with typedef name formats. We've FOO, Foo,
and foo_t. We tried to hash this out before, but we didn't come to a
clear
consensus. (We got sidetracked
UIntval
+typedef FLOATVAL Floatval
+typedef VTABLE VTable
+typedef DPOINTER DPointer
+typedef SYNC Sync
+
/* typedef INTVAL *(*opcode_funcs)(void *, void *) OPFUNC; */
#define FRAMES_PER_CHUNK 16
--
Bryan C. Warnock
[EMAIL PROTECTED]
the stuff you've a grief with now.
Let's make whatever changes to the coding standards that we need to do, and
move on from there. We need to start cracking the whip now. I'll take
responsbility for refactoring the old code.
--
Bryan C. Warnock
[EMAIL PROTECTED]
worked without a lot of hackery. (Not
that it's not a valid scenario. I've worked on a couple projects like that.)
Is this something we should at least look at?
--
Bryan C. Warnock
[EMAIL PROTECTED]
((start_stack != cur_stack) || (chunks_traced == 0))) {
-for (i = 0; i STACK_CHUNK_DEPTH; i++) {
+for (i = 0; i cur_stack-used; i++) {
if (STACK_ENTRY_STRING == cur_stack-entry[i].flags) {
buffer_lives((Buffer *)cur_stack-entry[i].entry.string_val);
}
--
Bryan C
= { # stack[43]
num_val = 1.0955949148585e-307
int_val = 3387912
pmc_val = 0x33b208
string_val = 0x33b208
generic_pointer = 0x33b208
}
..
..
..
--
Bryan C. Warnock
[EMAIL PROTECTED]
== cur_stack-entry[i].entry_type) {
buffer_lives((Buffer *)cur_stack-entry[i].entry.string_val);
}
}
--
Bryan C. Warnock
[EMAIL PROTECTED]
*/
if (type entry-entry_type != type) {
@@ -189,8 +197,6 @@
(*entry-cleanup) (entry);
}
-/* Now decrement the SP */
-chunk-used--;
/* Sometimes the caller doesn't care what the value was */
if (where == NULL)
--
Bryan C. Warnock
[EMAIL PROTECTED]
, however one is as good as another here.
and both will be going away.
(I hope that 0.0.4 and my schedule sync up the way I need it to.)-:
--
Bryan C. Warnock
[EMAIL PROTECTED]
?
--
Bryan C. Warnock
[EMAIL PROTECTED]
1 - 100 of 434 matches
Mail list logo
