Luke Palmer <[EMAIL PROTECTED]> wrote:
> I wonder if there is a macroey thing that we can do here. That is,
> could we make:
>
> ok(1);
> is(1, 1);
> like("foo", /foo/);
>
> Into:
>
> ok(1);
> ok(1 == 1);
> ok("foo" ~~ /foo/);
>
> And lexically analyze the argument to ok()
On 12/5/05, Darren Duncan <[EMAIL PROTECTED]> wrote:
> Under the current system, a subroutine argument is an alias for the
> container passed to it;
The most immediate offender here is the referential passing semantics.
Here is a code case:
sub foo ($x, &code) {
&code();
say
On Sun, 2005-12-04 at 12:25 +0100, Leopold Toetsch wrote:
> And it doesn't answer my question at all, sorry. Which HLLs are able to
> divide their symbols into above categories?
Ah, maybe I see what you're getting at.
At compile-time, a HLL knows whether it is compiling a sub or a
variable. But
On Sun, Dec 04, 2005 at 06:37:25PM +0100, Leopold Toetsch wrote:
> This is an unordered collection of my thoughts towards a next release:
> * config module cleanup: auto/jit.pm and gen/icu.pm comes to my mind
> (and why /gen anyway?)
Not just the steps themselves need work, there is still some fa
My test suite at work was starting to get me down. It was taking
forever to run. Not just the whole suite mind you, but individual
scripts were taking several seconds just to start up.
As my application has grown, so has its library (including a lot of
interconnected Class::DBI modules), and th
"Leopold Toetsch" <[EMAIL PROTECTED]> wrote:
* interfaces: start some brainstorming, what we might need in Parrot core
Having these would be great for the work I'm doing on the .NET => PIR
translator. Also I would really like to have support for:-
* Static methods
* Class level attributes (as
# New Ticket Created by David Dyck
# Please include the string: [perl #37841]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37841 >
---
osname= linux
osvers= 2.4.32
arch= i686-linux
cc= cc
---
Flags:
category=c
HaloO,
Luke Palmer wrote:
The most immediate offender here is the referential passing semantics.
IIRC, the default is to be a read-only ref. Not even local modifications
are permitted if the 'is copy' property is missing.
Here is a code case:
sub foo ($x, &code) {
&code();
TSa skribis 2005-12-05 12:32 (+0100):
> IIRC, the default is to be a read-only ref. Not even local modifications
s/ref/alias/, which you can see as an implicit or automatic reference,
but which we usually don't call that.
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl
I'm having some trouble accessing elements of multidimensional arrays
from PIR, and I'm not sure if what I want to do is buggy or
unimplemented, or if I'm simply doing it the wrong way.
I have no problem accessing a one-dimensional Array with either an
integer index, or with a PMC index of type In
HaloO,
Darren Duncan wrote:
The problem is that $! is being treated too much like a global variable
and not enough like a lexical variable. Consider the following example:
Wasn't the idea to have $! only bound in CATCH blocks?
sub foo () {
try {
die MyMessage.new( 'key' => 'dan
On Mon, Dec 05, 2005 at 12:32:03PM +0100, TSa wrote:
> HaloO,
>
> Luke Palmer wrote:
> >The most immediate offender here is the referential passing semantics.
>
> IIRC, the default is to be a read-only ref. Not even local modifications
> are permitted if the 'is copy' property is missing.
>
>
>
HaloO,
Nicholas Clark wrote:
No, I think not, because the closure on the last line closes over a
read/write variable. It happens that read only reference to the same variable
is passed into the subroutine, but that's fine, because the subroutine never
writes to *its* reference.
So, you argue t
On Dec 5, 2005, at 13:50, Roger Browne wrote:
I'm having some trouble accessing elements of multidimensional arrays
from PIR, and I'm not sure if what I want to do is buggy or
unimplemented, or if I'm simply doing it the wrong way.
$S0 = array[$P0; $P1] # [1]
Multi-dimensional keys
On Dec 5, 2005, at 8:03, David Dyck (via RT) wrote:
checked out todays version and found the following build error:
src/embed.c: In function `Parrot_readbc':
src/embed.c:373: `MAP_FAILED' undeclared (first use in this function)
Strange. Which linux and libc version is this?
Anyway, I've ch
Leopold Toetsch wrote:
> ... it's probably simpler to just teach your compiler to use
> integers/strings rather than PMCs.
In general, I don't think a HLL has enough information to do this.
For example, if you have an Array of Hashes, the HLL doesn't easily know
to convert to an integer for the
On 12/5/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> Not just the steps themselves need work, there is still some fairly
> substantial work left to be done on the configure framework as part of
> my refactoring project. This has been going rather slowly because it's
> usually bad to major radic
On Sun, Dec 04, 2005 at 01:10:44PM -0500, Mike Li wrote:
> what is a good translation of the following C into perl6?
[snip]
>
> in perl5, i would've written something like:
>
>
> my $x = 0; my @y = 1..9; @y[$x++]++; print "$x\n"; print "@y\n"
>
>
> but in perl6, the '@' sigil always means list
On Dec 5, 2005, at 5:55, Matt Diephouse wrote:
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Of course, now that I think about it more, it's possible that nothing
else will be adding namespaces for Python.
Or: only python itself can create Python namespaces.
In which case I'd advocate
havin
this is an older slackware derivative with one of the last libc5 systems,
May 13 1998 libc.so.5 -> libc.so.5.4.44*
Feb 1 1998 libc.so.5.4.44*
but it does use recent (2.4.32) kernel header files.
On Mon, 5 Dec 2005 at 06:34 -0800, Leopold Toetsch via RT
From: Leopold Toetsch via RT <[
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #37845]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37845 >
- I've e.g. a fully uptodate and built r10349.
- svn up to r10350
- I see a change i
My gut-level feeling on this is that $! is going to end up being an
"env" variable like $_. (If you don't know what "env" is then you've
not read the conjectural parts of S2 lately.) Then the problem reduces
to what you do with an unhandled $! at the end of a lexical scope,
which is probably just
> > $S0 = array[$P0; $P1]
Leo suggested:
> ... If you really need a PMC for the key, you
> have to create a Key PMC yourself.
>
> E.g.
>
>k1 = new .Key
>k1 = 1
That fragment works OK, but if I try to use a PMC instead of a literal
integer...
k1 = new .Key
$P0 = new .Intege
On Sat, 3 Dec 2005, Leopold Toetsch via RT wrote:
>
> On Dec 2, 2005, at 19:59, Andy Dougherty (via RT) wrote:
>
> > Parrot_jit_emit_mov_mr_offs blib/lib/libparrot.a(jit.o)
> > Parrot_jit_emit_get_base_reg_no blib/lib/libparrot.a(jit.o)
> > Parrot_jit_emit_mov_mr_n_offs blib/li
hi,
attached is a patch that adds the new ".lex" syntax. The description is
copy/paste from PDD20.
regards,
klaas-jan
--- imcc/docs/syntax.pod2005-12-05 19:49:30.0 +0100
+++ imcc/docs/syntax2.pod 2005-12-05 20:15:53.0 +0100
@@ -207,6 +207,25 @@
them with commas:
On 12/5/05, Klaas-Jan Stol <[EMAIL PROTECTED]> wrote:
> hi,
>
> attached is a patch that adds the new ".lex" syntax. The description is
> copy/paste from PDD20.
>
thanks, applied to docs/imcc/syntax.pod as r10354.
it seems mail from RT is a little slow, so you may not have been aware
of the recent
On Dec 5, 2005, at 18:28, Andy Dougherty wrote:
On Sat, 3 Dec 2005, Leopold Toetsch via RT wrote:
Can you provide dummy subs for the _offs functions and put in a dummy
define for the get_base_reg_no macro that returns some valid register
number.
I'll try something, but it'll be nearly blin
On Dec 5, 2005, at 18:11, Roger Browne wrote:
Maybe multidimensional array access using PMC indexes isn't supposed to
be working yet.
I see. Yes you are right. You really can rigth now do the 'easy' cases,
where a compiler knows or infers the involved types, but a general
multi-dim array ac
n 11/29/05, via RT jerry gay <[EMAIL PROTECTED]> wrote:
> this will likely require configure, makefile, build, and documentation
> modifications. related is moving the tools/* files to the proper
> subdirs, and renaming them where appropriate. this should be grouped
> with other tools/-related modi
hi,
if I understood correctly, the global storage is implemented as a hash
table.
If so, will it be possible to load this global hash table in a P register?
So, for example, are there any plans to support this:
$P0 = get_globals # put a reference to the global storage into
register $P0
applied as r10353.
i made some formatting changes and updated links in the documents, and
had to modify the manifest and some html document generation code. all
in all, a pretty simple change.
it would be great if somebody could take a look at the docs as a whole
and rework them where necessary (
Perhaps docs/pir would be better as I can't think of a reason to salt
the user docs with references to imcc.
Cheers,
-J
--
On Mon, Dec 05, 2005 at 09:48:53AM -0800, Jerry Gay via RT wrote:
> applied as r10353.
>
> i made some formatting changes and updated links in the documents, and
> had to m
i will be beginning this task soon. i expect it won't affect the build
much, as it's a docs dir, but be aware.
~jerry
I am performing some basic arithmetic on some variables and then using
a numeric equality operator to see if it returns what I think it should
by.
I am printing out the results and sure enough it is as expected. My
problem is when I use the numeric equality operator it returns false
even though my
On Mon, 2005-12-05 at 11:48 -0800, [EMAIL PROTECTED] wrote:
> I am performing some basic arithmetic on some variables and then using
> a numeric equality operator to see if it returns what I think it should
> by.
> I am printing out the results and sure enough it is as expected. My
> problem is wh
On Mon, Dec 05, 2005 at 07:54:25AM +, Luke Palmer wrote:
> I wonder if there is a macroey thing that we can do here. That is,
> could we make:
>
> ok(1);
> is(1, 1);
> like("foo", /foo/);
>
> Into:
>
> ok(1);
> ok(1 == 1);
> ok("foo" ~~ /foo/);
>
> And lexically ana
Nathan Gray:
> Luke Palmer:
>> I wonder if there is a macroey thing that we can do here. That is,
>> could we make:
>>
>> ok(1);
>> is(1, 1);
>> like("foo", /foo/);
>>
>> Into:
>>
>> ok(1);
>> ok(1 == 1);
>> ok("foo" ~~ /foo/);
>>
>> And lexically analyze the argument
Sorry, I tried to follow docs/submissions.pod, but my patch-fu is
very weak. Please forgive me.
This is a test for C3 MROs, it includes most of the tests from
Perl6::MetaModel prototype in Pugs (which themselves were stolen from
examples in Python and Dylan).
I am not sure where you would
On Mon, 2005-12-05 at 07:54 +, Luke Palmer wrote:
> I wonder if there is a macroey thing that we can do here. That is,
> could we make:
>
> ok(1);
> is(1, 1);
> like("foo", /foo/);
>
> Into:
>
> ok(1);
> ok(1 == 1);
> ok("foo" ~~ /foo/);
Can you do it without givin
39 matches
Mail list logo
