In message <[EMAIL PROTECTED]>
Brian Wheeler <[EMAIL PROTECTED]> wrote:
> Darn it, I fat fingered the log message.
>
> This is a fix which changes the way op variants are handled. The old
> method "forgot" the last variant, so thing(i,i|ic,i|ic) would
> generate:
> thing(i,i,i)
> thin
Darn it, I fat fingered the log message.
This is a fix which changes the way op variants are handled. The old
method "forgot" the last variant, so thing(i,i|ic,i|ic) would
generate:
thing(i,i,i)
thing(i,i,ic)
thing(i,ic,i)
but not
thing(i,ic,ic)
The new one does.
Brian
At 11:59 PM 10/25/2001 +0100, Tom Hughes wrote:
>In message <[EMAIL PROTECTED]>
> Dan Sugalski <[EMAIL PROTECTED]> wrote:
>
> > =item type
> >
> > What the character set or type of data is encoded in the buffer. This
> > includes things like ASCII, EBCDIC, Unicode, Chinese Traditional,
>
Yeah, I probably should have named the register stack 'X' or something like
that. At least we're thinking along somewhat compatible lines. I'll be eager to
see your solution...
Dan Sugalski wrote:
> At 10:34 AM 10/25/2001 -0400, Jeffrey Goff wrote:
> >pope # Resto
With the patch attached, all tests pass on Win32.
Well, except for the fact that classes\intclass.obj gets created as
.\intclass.obj, forcing you to manually copy it to the right place.
Ugh. And examples\assembly\mops.obj has the same problem. And there
are 11 warnings in intclass.c that I don'
In message <[EMAIL PROTECTED]>
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> =item type
>
> What the character set or type of data is encoded in the buffer. This
> includes things like ASCII, EBCDIC, Unicode, Chinese Traditional,
> Chinese Simplified, or Shift-JIS. (And yes, I know the lat
Here's a list of what I'm going to try and get done really soon (like in
the next day or so)
*) Toss that stupid interpreter parameter. Going with thread-local storage
instead. (And I know this is going to make Win32 unhappy)
*) Split the generic stack into a temp stack and control stack
*) Def
At 10:34 AM 10/25/2001 -0400, Jeffrey Goff wrote:
>pope # Restore the exception stack
I've been thinking about going with an exception stack rather than a set of
exception registers, but there's something awfully compelling about an
opcode named "pope"... :)
[Apologies if this is a repeat, but the last message was early Wed. and
hasn't gone through yet]
The promised patches (against Wednesday morning's CVS-latest) are
attached to this message.
[You might need to reverse the first patch, against MANIFEST]
These patches add the following:
a) Exceptio
The included patch requires a new file t/op/exceptions.t, which tests basic exception
handling, in this case divide-by-zero.
Patch was generated against latest CVS, but it shouldn't matter -that- much.
-Jeff
<[EMAIL PROTECTED]>
diff --recursive -C 2 parrot_cvs/MANIFEST parrot/MANIFEST
*** pa
At 12:24 PM 10/25/2001 -0700, Russ Allbery wrote:
>Dan Sugalski <[EMAIL PROTECTED]> writes:
> > At 08:59 AM 10/25/2001 -0400, Andy Dougherty wrote:
>
> >> Then we probably should change Parrot's name of BOOL. I'd
> >> suggest Bool_t, modeled after perl5's Size_t (and similar "types").
>
> > Sound
Dan Sugalski <[EMAIL PROTECTED]> writes:
> At 08:59 AM 10/25/2001 -0400, Andy Dougherty wrote:
>> Then we probably should change Parrot's name of BOOL. I'd
>> suggest Bool_t, modeled after perl5's Size_t (and similar "types").
> Sounds like a good idea.
IIRC, all types ending in _t are reserve
At 12:19 PM 10/25/2001 -0400, Sam Tregar wrote:
>On Thu, 25 Oct 2001, Dan Sugalski wrote:
>
> > The only bits of the interpreter that much care about the
> > string data are the regex engine parts, and those only operate on
> > fixed-sized data.
>
>Care to elaborate? I thought the mandate from La
On Thu, 25 Oct 2001, Dan Sugalski wrote:
> The only bits of the interpreter that much care about the
> string data are the regex engine parts, and those only operate on
> fixed-sized data.
Care to elaborate? I thought the mandate from Larry was to have regexes
compile down to a stream of string
'Kay, here's the string background info I promised. If things are missing
or unclear let me know and I'll fix it up until it is.
==Cut here with a very sharp knife===
=head1 TITLE
A parrot string backgrounder
=head1 Overview
Strings, in parrot, are compartmentaliz
l1:/pro/3gl/CPAN/parrot-current 102 > make distclean
perl -MExtUtils::Manifest=filecheck -le 'xtUtils::Manifest::Quiet=1;unlink for
filecheck()'
Undefined subroutine &xtUtils::Manifest::Quiet called at -e line 1.
make: *** [distclean] Error 255
l1:/pro/3gl/CPAN/parrot-current 103 > rm -f *.o *.a
At 08:59 AM 10/25/2001 -0400, Andy Dougherty wrote:
>In perl.perl6.internals, you wrote:
> >On Wed, 24 Oct 2001, Brent Dax wrote:
> >
> >>Unfortunately, I can't figure out how to utilize it. Including
> >>windows.h causes a conflict with Parrot's definition of BOOL, including
>
>Then we probably
At 02:28 AM 10/25/2001 +0200, Espen Harlinn wrote:
>Instead of thinking about multiple threads, one could think about multiple
>execution contexts. Each instance of an object must belong to one and only
>one execution context. Each execution context has an attached security
>context and a security
At 07:13 PM 10/24/2001 -0700, Brent Dax wrote:
>Espen Harlinn:
># Here is just a proposal:
>#
># 1. Place os neutral code in one directory
># 2. place os dependant code in platform specific directories
>
>What about little inline things?
>
>AUTO_OP sleep(i|ic) {
> #ifdef WIN32
>
On Thu, Oct 25, 2001 at 09:47:01AM -0400, James Mastros wrote:
> This is version 0.4 of my chr and ord patch for parrot. Included is a
> patch, a test file, and an example.
That one looks good. You know, if it had documentation, I'd commit it. :)
--
A language that doesn't have everything is
Hey all.
This is version 0.4 of my chr and ord patch for parrot. Included is a
patch, a test file, and an example.
I don't really see any major problems with this version, at least that
aren't implicit in the current Way Of Things with strings. (That is, native
not being explicitly anything,
In perl.perl6.internals, you wrote:
>On Wed, 24 Oct 2001, Brent Dax wrote:
>
>>Unfortunately, I can't figure out how to utilize it. Including
>>windows.h causes a conflict with Parrot's definition of BOOL, including
Then we probably should change Parrot's name of BOOL. I'd
suggest Bool_t, model
Espen Harlinn:
# Brent Dax:
# > What about little inline things?
# >
# > AUTO_OP sleep(i|ic) {
# > #ifdef WIN32
# > Sleep($1*1000);
# > #else
# > sleep($1);
# > #endif
# > }
#
# As long as the file compiles on all platforms, I think it's logical to
# consider it
In perl.perl6.internals, you wrote:
>Brent Dax <[EMAIL PROTECTED]> writes:
>
>> What about little inline things?
>
>> AUTO_OP sleep(i|ic) {
>> #ifdef WIN32
>> Sleep($1*1000);
>> #else
>> sleep($1);
>> #endif
>> }
>
>This reminds me. gcc is slowly switching
Brent Dax:
> What about little inline things?
>
> AUTO_OP sleep(i|ic) {
> #ifdef WIN32
> Sleep($1*1000);
> #else
> sleep($1);
> #endif
> }
As long as the file compiles on all platforms, I think it's logical to
consider it platform independant :-)
Bre
On Wed, 24 Oct 2001, Brent Dax wrote:
>Unfortunately, I can't figure out how to utilize it. Including
>windows.h causes a conflict with Parrot's definition of BOOL, including
>winbase.h gives me a ton of syntax errors, and putting the declaration
It is not supported to #include a win* file unles
26 matches
Mail list logo
