At 9:58 AM +0200 8/1/04, Leopold Toetsch wrote:
Jerry Gay <[EMAIL PROTECTED]> wrote:
Leopold Toetch wrote:
Both ways - or better three stages: Its optional. If its
there, we *can* link against it. If you want/need it, and
your OS doesn't have it, well, then install it.
and if you don't want
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> ... and therefore ICU will continue to stay in CVS
> as part of parrot. Period.
>
> The alternative here is the same alternative as with
> GMP and big numbers--we can yank ICU *if* someone
> writes an alternate Unicode implementation for us.
> --
>
I got asked a lot at OSCON, and this has been something of a topic on
and off on the list. I've committed a DESIGN_TODO file with brief
details of what I think still needs working on, which I'll be adding
to as things make themselves obvious (I've got a bigger list on paper
this morning) so the
At 6:20 AM -0700 8/3/04, Joshua Gatcomb wrote:
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
... and therefore ICU will continue to stay in CVS
as part of parrot. Period.
The alternative here is the same alternative as with
GMP and big numbers--we can yank ICU *if* someone
writes an alternate Un
Dan Sugalski sent the following bits through the ether:
> If someone's tempted to do 3) Write our own Unicode system, I'm OK
> with that too. The string internals doc needs writing, and I can get
> that done.
IIRC the mono people wrote their own, but with the ICU data files.
Apart from license
Joshua Gatcomb wrote:
> Dan Sugalski wrote:
> > ... and therefore ICU will continue to stay in CVS as part of
> > parrot. Period.
> >
> > The alternative here is the same alternative as with GMP and big
> > numbers--we can yank ICU *if* someone writes an alternate Unicode
> > implementation for
I know this was discussed earlier, but I think its still an issue.
First python's usage of values aka builtin objects:
1) almost all opcodes create a new object as result (the value)
2) LOAD_NAME | STORE_NAME (or _GLOBAL or _FAST) opcodes deal with
variables, the value is fetched or stored from lo
On Tue, Aug 03, 2004 at 03:09:02PM +0100, Leon Brocard wrote:
> Dan Sugalski sent the following bits through the ether:
>
> > If someone's tempted to do 3) Write our own Unicode system, I'm OK
> > with that too. The string internals doc needs writing, and I can get
> > that done.
>
> IIRC the m
In what's seems a rather bizarre twist, Parrot's getting production
ready. Yes, I find this really strange, and no, I'm not even talking
about my work project, though I probably should. Python and PHP are
both near-beta ready, and Span looks... well, it looks damn nice.
As such, I think we're i
I've had this list lying around for too long, but never seem to find
time to make it all shiny and complete.
I want to have another go at the html documentation. But before I start
I'd prefer to have a good list of everything Parrot. That way I can
build a proper subject view of the project.
I
[Tue, Aug 03, 2004 at 07:45:57PM +0100: Nicholas Clark]
> On Tue, Aug 03, 2004 at 03:09:02PM +0100, Leon Brocard wrote:
> > Dan Sugalski sent the following bits through the ether:
> >
> > > If someone's tempted to do 3) Write our own Unicode system, I'm OK
> > > with that too. The string int
Although I sent this ideas to this list, with another subject, here they
go again to enter in the correct thread.
I think that to have ICU included both in CVS and tarballs created for
parrot is not the best way. I know Dan (and maybe some others) do not
want to depend on too much libraries. Th
At 7:22 PM +0100 8/3/04, Alberto Manuel Brandao Simoes wrote:
Although I sent this ideas to this list, with another subject, here
they go again to enter in the correct thread.
I think that to have ICU included both in CVS and tarballs created
for parrot is not the best way. I know Dan (and maybe
At 18:46 on 08/03/2004 EDT, Dan Sugalski <[EMAIL PROTECTED]> wrote:
> If someone's got the time and I spec out the encoding and charset
> APIs, I'd be thrilled if ICU became optional again. Wouldn't hurt my
> feelings at all. We need it, because we need Unicode, but it doesn't
> have to be req
Dan --
Thanks for mentioning Jako. It usually gets no respect. :)
But, I think Jako is "working" for some definition of "working". But, it
is clearly not an idiomatic compiler in that its using old conventions
(not surprising, given its history).
Did I miss the creation of the compiler-writer list?
Hello, folks.
Just wanted to let people know, I've been following parrot and reading the
list for a while now, but just recently I finally co'd a copy of parrot and
decided it was time that i actually did something with it. The first thing I
did was do some work on making it nice in the editor
Josh Wilmes wrote:
If someone's got the time and I spec out the encoding and charset
APIs, I'd be thrilled if ICU became optional again. Wouldn't hurt my
feelings at all. We need it, because we need Unicode, but it doesn't
have to be required.
We'll need something that isn't ICU if we're going t
On Tue, Aug 03, 2004 at 11:32:33PM +0100, Alex Gough wrote:
> For what it's worth, I checked a parrot out for the first time in ages
> a couple of days ago (the Shub-tuit gives, as the Shub-tuit takes
> away...), but got all stuck failing to work out how to get icu not to
> be a problem, and so get
In his latest Perl 5 Bug Summary, Robert Spier listed the following bugs. I seem to
recall that
patches were sent to perl-qa to resolve these. Were they not applied or were the bugs
not closed?
(Or were they not sent and I'm enjoying a touch too much wine here?)
30576 Test::More thinks "" e
Hi all,
I'd like to register some subroutines defined in PASM (or better, PIR)
as participating in multiple dispatch. This is very handy when writing
Test::Builder::is(), for example, which can compare two strings,
integers, numbers, or PMCs, or for calling NCI functions which can take
various ty
At 05:13 PM 8/3/2004 -0700, Gregor N. Purdy wrote:
Did I miss the creation of the compiler-writer list? I need to figure
No, we are still holding our breath (and turning blue, purple, green, ...)
Btw, I'll poke the Cola rewrite I have here and see where it stands. It
gathered a bit of dust in the p
# New Ticket Created by chromatic
# Please include the string: [perl #30946]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=30946 >
Hi there,
Here's a small patch that adds syntax highlighting to macros in .imc and
.pir
> CVS ci rights for Jarkko would be fine,
Please send all requests like (and including) this one to cvs at
perl.org.
-R
23 matches
Mail list logo
