On Thursday, Sep 25, 2003, at 00:41 Europe/Berlin, Robert Spier wrote:
Which version of ICU is in parrot/icu. Maybe 2.6 would be the most
likely to build.
As an update would probably best be done by delete and replace,
perhaps
it could coincide with the great renaming?
Actually, it would be best
I have a question/request concerning perl6 object properties.
I've done some work with .NET and They have come up with a really slick way
to handle object properties.
A typical property definition in VB.NET looks like:
Public Property description() As String
Get
return aString
End Get
I have a question/request concerning perl6 object properties.
I've done some work with .NET and They have come up with a really slick
way to handle object properties.
A typical property definition in VB.NET looks like:
Public Property propertyName() As String
Get
return aString
End Get
Todd W. writes:
I have a question/request concerning perl6 object properties.
Rather, attributes. Properties are out-of-band data attached to a
particular object.
I've done some work with .NET and They have come up with a really slick way
to handle object properties.
A typical property
On Wed, Sep 24, 2003 at 07:53:39PM -0400, Todd W. wrote:
I posted a question to CLPM on how to do this with perl5 and we decided to
use an 'lvalue' attribute on the subroutine and then make the returned
lvalue in the sub a tied variable to intercept read/writes:
i tried to build a program and have only one error but seem not to be able to fix it.
i think it is a rather small one. i would really appreciate it if you help me with
this situation:
if (num1 %2 =0)
the error is: error C2106: '=' : left operand must be l-value.
thank you very much. i
On Wed, 24 Sep 2003, Todd W. wrote:
I have a question/request concerning perl6 object properties.
I've done some work with .NET and They have come up with a really slick way
to handle object properties.
A typical property definition in VB.NET looks like:
Public Property description()
On Thu, 25 Sep 2003, Luke Palmer wrote:
Todd W. writes:
I have a question/request concerning perl6 object properties.
Rather, attributes. Properties are out-of-band data attached to a
particular object.
FWIW, attribute and property are two words that have a meaning that
shifts depending
: [EMAIL PROTECTED] (Luke Palmer) writes:
:
:
: I would hope the former. However, what about this compile-time
: integral power macro[1]?
:
:macro power ($x, $p) {
:if $p 0 {
:{ $x * power($x, $p-1) }
:}
:else {
:{ 1 }
:}
:}
On Mon, Sep 08, 2003 at 11:18:12AM +0200, Paul Johnson wrote:
: By the way, I trust this will be addressed (if it hasn't been already):
:
: perl5 -le 'print gah! if exists $a{b}{c}; print phooey! if exists $a{b}'
:
: perlfunc says:
:
: This surprising autovivification in what does not at
Sorry, I've been following this list
with one eye tied behind my back...
What happened to setline? Should I
emit something else instead?
Sincerely,
Michal J Wallace
Sabren Enterprises, Inc.
-
contact: [EMAIL PROTECTED]
hosting: http://www.cornerhost.com/
At 7:48 PM -0400 9/25/03, Michal Wallace wrote:
Sorry, I've been following this list
with one eye tied behind my back...
What happened to setline? Should I
emit something else instead?
It's never really been the right thing to do, but we've not got the
alternative, line metadata in the bytecode
Hi:
In case it helps, it looks like it's crashing at string.c:552, because
it's trying to call src-encoding-decode() but src-encoding is NULL.
(gdb) f 0
#0 0x6104 in string_transcode (interpreter=0x616400, src=0x623440,
encoding=0x19e43c, type=0x19a6fc, dest_ptr=0x0) at string.c:552
552
Luke Palmer wrote:
Dan Sugalski writes:
... For this, I think we're
going to need a setp Ix, Py op which does indirect register addressing.
Fair enough. I do suppose there will be a way to keep the register
allocation intact while doing this. Or maybe these ops are for IMCC's
personal use,
On Wed, 2003-09-24 at 11:08, Leopold Toetsch wrote:
Further: as URM has an arbitrary amount of registers, it would be much
simpler to target PIR code.
r46 - r100 + r200
is currently for sure an error. OTOH translating this to
$I46 = $I100 + $I200
Ok, fixed that and some other
Michael Scott [EMAIL PROTECTED] wrote:
t/src/hash.t
test 7 fails on Mac OS X 10.2.6 (gcc 3.3) because BIGLEN is too big:
9.
100_000 chars for the key doesn't seem to be very big.
Wher does it fail?
Can you debug/back-trace it?
I've made it a bit smaller: 65536.
This begs the
Here are some tests for the io.h API that should go in t/src/io.t.
Maybe some of the expected results are debatable.
Should PIO_parse_open_flags think that is the same as ?
Should PIO_fdopen open ok on stdout with invalid flags like ;-) or ?
Also, successive calls to PIO_seek with SEEK_CUR
Marcus Thiesen wrote:
On Wed, 2003-09-24 at 11:08, Leopold Toetsch wrote:
$I46 = $I100 + $I200
Ok, fixed that and some other issues Leo addressed. Now I have my own
register management and put all the not needed registers on the user
stack.
Why? Parrot with the PIR assembler can handle an
# New Ticket Created by Michael Scott
# Please include the string: [perl #24038]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24038
PIO_parse_open_flags thinks that is the same as . This
could lead to errors such
On Thu, 2003-09-25 at 15:10, Leopold Toetsch wrote:
Ok, fixed that and some other issues Leo addressed. Now I have my own
register management and put all the not needed registers on the user
stack.
Why? Parrot with the PIR assembler can handle an arbitrary register
count. I'm sure you
Dan Sugalski wrote:
...I can, and have, written the C code to make this happen
in build_nativecall.pl, but that doesn't help on the x86 platforms which
build this stuff up dynamically.
You allways can edit nci.c (or build_nativecall.pl) and undef (or mangle
the define of)
Dan Sugalski wrote:
Okay, we're starting to get some library code. I've a full (hopefully)
ncurses interface .pasm file
The ncurses lib is reall great.
lib/ subdirectory for assembly and/or imcc library code?
I'd rather kept all that stuff in runtime/parrot/* where there are
already things
On Thursday, Sep 25, 2003, at 13:20 Europe/Berlin, Leopold Toetsch
wrote:
Michael Scott [EMAIL PROTECTED] wrote:
t/src/hash.t
test 7 fails on Mac OS X 10.2.6 (gcc 3.3) because BIGLEN is too big:
9.
100_000 chars for the key doesn't seem to be very big.
Wher does it fail?
Can you
On Thu, 25 Sep 2003, Leopold Toetsch wrote:
Dan Sugalski wrote:
...I can, and have, written the C code to make this happen
in build_nativecall.pl, but that doesn't help on the x86 platforms which
build this stuff up dynamically.
You allways can edit nci.c (or build_nativecall.pl)
On Thu, 25 Sep 2003, Leopold Toetsch wrote:
Dan Sugalski wrote:
Okay, we're starting to get some library code. I've a full (hopefully)
ncurses interface .pasm file
The ncurses lib is reall great.
:) Now we can have multicolored life! Woohoo!
lib/ subdirectory for assembly and/or
On Thursday, Sep 25, 2003, at 16:06 Europe/Berlin, Michael Scott wrote:
On Thursday, Sep 25, 2003, at 13:20 Europe/Berlin, Leopold Toetsch
wrote:
Michael Scott [EMAIL PROTECTED] wrote:
t/src/hash.t
test 7 fails on Mac OS X 10.2.6 (gcc 3.3) because BIGLEN is too big:
9.
100_000 chars for
Dan Sugalski [EMAIL PROTECTED] wrote:
Fair enough. I'd not realized we had a runtime directory.
BTW some warnocked stuff:
Date: Sat, 23 Aug 2003 17:01:36 +0200
From: Leopold Toetsch [EMAIL PROTECTED]
Subject: some fun SubProxy
,--[ orig text
Michael Scott [EMAIL PROTECTED] wrote:
Program received signal EXC_BAD_ACCESS, Could not access memory.
0x5f30 in string_transcode ()
(gdb) bt
#0 0x5f30 in string_transcode ()
Thanks for the backtrace - doesn't help much though.
Anyway I've commited a patch to reenable 'debugging'
Unless you meant remove from the repository, such that it never
existed in the first place when you said delete.
Yes, I meant that.
That's quite doable, if people understand the repercussion. (rm -r
is easy!)
Say we apply 2.6 over what is there and it doesn't build, we then have
to
On Thu, 25 Sep 2003, Robert Spier wrote:
Say we apply 2.6 over what is there and it doesn't build, we then have
to ask ourselves if the applying-over's to blame. Just seemed like one
uncertainty that could be avoided.
Point.. although this can generally be done properly with a little
Ok. New ICU (2.6.1) has been committed.
-R
On Thu, 25 Sep 2003, Robert Spier wrote:
Ok. New ICU (2.6.1) has been committed.
Cool, thanks much.
Anyone care to take a shot at getting it building? (Might well be
dead-trivial, I don't know)
Dan
32 matches
Mail list logo
