Nick Glencross <[EMAIL PROTECTED]> wrote:
> This patch fixes a problem which can occur in this example:
> .sub test
> .const float a = 12
> print a
> print_newline
> .end
Ah yep.
>
> +if (t != 'P' && t != val->set)
> +IMCC_fataly(interp, E_TypeError,
> +
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #34994]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34994 >
A Python example first:
$ python
>>> import sys
>>> print sys.maxint
2147483647
hi,folks.
I am reading PMC C source code and reading some document("
http://www.perl.com/pub/a/2002/01/30/pmcs.html";).
Some questions:
*this PMC design have changed?
*any body offer some advice that learn PMC C source code and PMC's theory?
Thanks.
/\ /\
/ |
# New Ticket Created by Nick Glencross
# Please include the string: [perl #34991]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34991 >
Here's another odd one, which looks const-related. Uncommenting the '+='
line causes
On Thu, 31 Mar 2005 21:17:39 -0500, [EMAIL PROTECTED] (MrJoltCola)
wrote:
> At 05:57 PM 3/31/2005, Nigel Sandever wrote:
> >Is Parrot bytecode reentrant?
>
> Yes.
>
> >That is, if I want to have two instances of a class in each of two
> >threads, will
> >the bytecode for the class need to be lo
Thank you, applied!
jens
hi,folks.
I am reading PMC C source code and reading some document("
http://www.perl.com/pub/a/2002/01/30/pmcs.html";).
Some questions:
*this PMC design have changed?
*any body offer some advice that learn PMC C source code and PMC's theory?
Thanks.
/*
p2p is a protocol or a compiler?
*/
Hi,
There will be a Parrot/PUGS Hack-a-thon at the Austrian Perl Workshop, which
takes place on 9th and 10th June in Vienna, Austria.
Autrijus Tang, Chip Salzenberg and Leo Toetsch will be there. You should be
there too :-)
I'll be there, too. ;)
Bye,
Andras
Someone's pointed this thread out to me, so I'm going to shove an oar in
following a few posts. I've done a fair bit of security work, so feel
free to ask me to explain, justify or provide references for anything.
On Wed, 2005-04-13 at 17:01 -0400, Dan Sugalski wrote:
> All security is done on a p
On Wed, 2005-04-13 at 17:51 -0400, Aaron Sherman wrote:
> On Wed, 2005-04-13 at 17:01, Dan Sugalski wrote:
> > So here's what I was thinking of for Parrot's security and quota
> > model. (Note that none of this is actually *implemented* yet...)
> [...]
> > It's actually pretty straightforward, the
Steven Philip Schubiger wrote:
[ cc'ed list, so that folks know about takers ]
On 15 Apr, Leopold Toetsch wrote:
: 5) along with bringing the config online, some cleanup and renaming
: wouldn't harm e.g. "iv" vs "opcode_t", "intvalsize" vs "intsize" vs
: "opcode_t_size" ...
This part seems appea
Nigel Sandever <[EMAIL PROTECTED]> wrote:
> When a sub that closes over a variable
> my $closure = 0;
> sub do_something {
> return $closure++:
> }
> is called from two threads, do the threads share a single closure or
> each get their own separate closure?
AFAIK
Cory Spencer <[EMAIL PROTECTED]> wrote:
> I'd like to announce the creation of the Parrot Common Lisp project, which
> aims to implement a significant subset of the Common Lisp language.
Wow. I can even do something with it:
$ ../parrot lisp.imc
-> (+ 2 5)
7
-> (list 1 2 3)
(1 . (2 . (3 . NIL)))
Continuing the MMD infix plan, we now have:
1) the subtract MMD functions are converted to the new function signature:
PMC* subtract(PMC* value, PMC* dest)
If C isn't NULL it's set to the result of the operation and the
result is returned. This is the existing behavior. The TODO new "n_sub"
opc
On Thu, 2005-04-14 at 09:51 -0700, Dave Whipp wrote:
> Dan Sugalski wrote:
>
> > All security is done on a per-interpreter basis. (really on a per-thread
> > basis, but since we're one-thread per interpreter it's essentially the
> > same thing)
> ...
> >* Number of open files
> >* IO ope
On Wed, 2005-04-13 at 22:03 -0400, Michael Walter wrote:
> Dan,
>
> On 4/13/05, Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > All security is done on a per-interpreter basis. (really on a
> > per-thread basis, but since we're one-thread per interpreter it's
> > essentially the same thing)
> Just to
On Thu, 2005-04-14 at 09:11 -0400, Dan Sugalski wrote:
> At 10:03 PM -0400 4/13/05, Michael Walter wrote:
> > > Each running thread has two sets of privileges -- the active
> >> privileges and the enableable privileges. Active privs are what's
> >> actually in force at the moment, and can be dr
Bloves Mr <[EMAIL PROTECTED]> wrote:
> hi,folks.
> I am reading PMC C source code and reading some document("
> http://www.perl.com/pub/a/2002/01/30/pmcs.html";).
Despite that the text is rather old, it's remarkably valid still.
> Some questions:
> *this PMC design have changed?
The internal la
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #34999]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34999 >
Some outdated files:
lib/Parrot/PackFile/*
lib/Parrot/PackFile.pm
lib/Parr
I'm not quite sure, but it seems that some of the MMD functions may
better be vtable methods:
- bitwise_sh[rl]*shift by anything other then int?
- bitwise_lsris missing generally
or even just a plain opcode only:
- logical_{or,and,xor} return a PMC depending on the boolean value
What
On 15 Apr, Leopold Toetsch wrote:
: That stuff is all in Perl code under the config dir, e.g:
:
: $ find config -type f | xargs grep -w intsize
This clarifies some of my unapproved assumptions, although src has
some files containing these keywords too.
: I think we should have:
:
:INTVAL_t
# New Ticket Created by FranÃois PERRAD
# Please include the string: [perl #35000]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35000 >
small mistake in [perl #34986] :
with ICU 3.2, the library icudata.lib is renamed i
I've corrected a few spelling and punctuation errors;
since I'm not done yet, I'd like to know, whether I should
continue, or if the general consensus is, that it's mostly
needless nitpicking.
Punctuation has only been corrected, if punctuation was already
partly present; if totally absent, I di
MMD subroutines "add" are done.
* removed all mathematical functions from Tcl scalars - all is inherited now
I forgot to mention in MMD 23:
* If you have an overriden __add or __subtract function, either defined
as @MULTI or registered via mmdvtregister, these functions must now
return the destin
According to Cory Spencer:
> I'd like to announce the creation of the Parrot Common Lisp project
Excellent!
> * It's not a compiler yet, although I've got plans for that down the
> road.
(declare (type PerlString s)) ? :-)
--
Chip Salzenberg- a.k.a. -<[EMAIL PROTE
One more, and my fingers & brain are getting tired of these changes.
If someone wants to continue (and complete it during night here ;-),
it's a simple job:
1) vtable.tbl
- change existing signature of next infix operation
- add inplace variant directly below it
2) imcc/parser_util.c:is_inf
15/04/2005 10:35:56, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
>Nigel Sandever <[EMAIL PROTECTED]> wrote:
>
>> When a sub that closes over a variable
>
>> my $closure = 0;
>> sub do_something {
>> return $closure++:
>> }
>
>> is called from two threads, do the threads
On Fri, 2005-04-15 at 05:38 -0700, François PERRAD wrote:
> small mistake in [perl #34986] :
> with ICU 3.2, the library icudata.lib is renamed icudt.lib.
Thanks, applied.
-- c
Leopold Toetsch via RT wrote:
Nick Glencross <[EMAIL PROTECTED]> wrote:
This patch fixes a problem which can occur in this example:
.sub test
.const float a = 12
print a
print_newline
.end
Ah yep.
+if (t != 'P' && t != val->set)
+IMCC_fataly(inter
(If anyone is able to track down aforementioned DOD/GC problems,
you'll earn my eternal gratitude.)
Can you please provide a code snippet that exhibits the error.
Just running the program gives me errors on both Linux/x86 and OS X.
Running with GC disabled works fine.
On OS X with GC e
Leopold Toetsch via RT wrote:
I think, we could be a bit more graceful here for I/N mismatch and set
for the above case the constant val->set to 'N'.
Let me redo that... I've just sent the wrong attachment which had a
typo in it ...
[This should really address rare but possible Unicode str
On Fri, Apr 15, 2005 at 07:26:56PM +0100, Nick Glencross wrote:
> +// Forbid assigning a string to anything other than a string const
> +// for now
In future, please don't use C99 comments.
(apart from that, I don't have the knowledge to comment on this patch)
Nicholas Clark
I've been working on a C-to-Parrot compiler (actually an IMC backend
for the LCC compiler), tentatively named Carrot, over the past week. It
can currently do some reasonably useful things, like running the Cola
compiler (with only a very small amount of cheating), but it has raised
a few queries:
On Fri, Apr 15, 2005 at 02:38:36PM +0200, Leopold Toetsch wrote:
: I'm not quite sure, but it seems that some of the MMD functions may
: better be vtable methods:
:
: - bitwise_sh[rl]*shift by anything other then int?
: - bitwise_lsris missing generally
:
: or even just a plain opcod
According to Philip Taylor:
> * I can usually handle unsigned numbers by pretending they're signed and
> using 'I' registers, but some things appear to be awkward without new
> ops - in particular, div and cmod, and le/lt/ge/gt comparisons. (As far
> as I can tell, those are the only ones C woul
From: Larry Wall <[EMAIL PROTECTED]>
Date: Fri, 15 Apr 2005 12:52:53 -0700
On Fri, Apr 15, 2005 at 02:38:36PM +0200, Leopold Toetsch wrote:
: I'm not quite sure, but it seems that some of the MMD functions may
: better be vtable methods:
:
: - bitwise_sh[rl]*shift by any
On 4/15/05, Shevek <[EMAIL PROTECTED]> wrote:
> > How can dropping a privilege for the duration of a (dynamic) scope be
> > implemented? Does this need to be implemented via a parrot intrinsic,
> > such as:
> >
> > without_privs(list_of_privs, code_to_be_run_without_these_privs);
> >
> > ..or is
37 matches
Mail list logo
