The assembler doesn't use the XS stuff anymore, just committed a patch
build from Jeff's code.
Let's hope to see some more tinderboxes green.
Daniel Grunblatt.
I decided my next step should be to take a look at the PDDs so I know what's
going on. I would expect them to be like a writer's canon for a TV show. I'll
write my impressions as I go on.
PDD00:
Does PDD still mean 'Perl Design Document', or should it mean 'Parrot ...'?
The documents seem to a
Brent Dax wrote:
> If people want that scheme, speak now or forever hold your peace.
Sounds reasonable to me. (FWIW)
> > _Parrot
> > _parrot
> > __Parrot
> > __parrot
>
> The last four are reserved by various C and C++ standards.
Damn, I forgot about that. I'm a C coder from Way Ba
At 09:27 PM 7/14/2002 -0700, Brent Dax wrote:
Wow, Brent lives! :)
>Here's the rules, roughly as they stand right now:
>
> -Functions start with Parrot_[a-z] or just [a-z].
> -Typedefed names start with Parrot_[A-Z] or just [A-Z].
> -Macros and constants start with PARROT
John Porter:
# Brent Dax wrote:
# > Ashley Winters:
# > > c. parrot_sprintf
# >
# > Lowercase is always the hallmark of struct names, i.e.
# > parrot_string_t.
#
# Ehhh... you yourself said something about plat_ and misc_
# as (theoretical) alternatives.
#
# Anyway, it's a silly rule. Upper-c
At 09:55 PM 7/14/2002 -0400, Josh Wilmes wrote:
>IMHO, there's no way to find out quite like trying to use it :)
>
>In my experiences with it thus far, it all seems to work fine. Melvin has
>indicated that its API and internal structure may need some changes at
>some point, but the basic function
Brent Dax wrote:
> Ashley Winters:
> > c. parrot_sprintf
>
> Lowercase is always the hallmark of struct names, i.e.
> parrot_string_t.
Ehhh... you yourself said something about plat_ and misc_
as (theoretical) alternatives.
Anyway, it's a silly rule. Upper-case (and lower-case) are
going to h
Ashley Winters:
# On Monday 15 July 2002 02:25 am, Brent Dax wrote:
# > -C library wrappers: This is Parrot's version of the
# function, so it
# > makes sense to prefix it with Parrot_.
# >
# > The third category I can see having a prefix of plat_ (for
# platform)
# > or some such, and perhap
[EMAIL PROTECTED]:
# Good stuff. Didn't you also send out a draft PDD about how
# types should
# be named and managed in parrot at one point? I, for one,
At one point I sent out a patch to PDD7 that handled type naming.
# would love to
# see a PDD that described C-level nanming and namespa
On Monday 15 July 2002 02:25 am, Brent Dax wrote:
> -C library wrappers: This is Parrot's version of the function, so it
> makes sense to prefix it with Parrot_.
>
> The third category I can see having a prefix of plat_ (for platform) or
> some such, and perhaps the second could have misc_, but I
John Porter:
# Brent Dax wrote:
# > > 2. What does having a Parrot_ prefix signify, considering
# > > both the opcodes and the embed api use it?
# >
# > It signifies one of the following:
# > -This function is externally visible.
# > -This function belongs to Parrot at large, and not any particul
# New Ticket Created by "Sean O'Rourke"
# Please include the string: [perl #815]
# in the subject line of all future correspondence about this issue.
# http://bugs6.perl.org/rt2/Ticket/Display.html?id=815 >
Should handle things like "1e8", but it now requires a decimal point.
/s
-- attach
On Sun, 14 Jul 2002, Mike Lambert wrote:
> There currently is a 'morph' vtable entry, which I believe is intended to
> morph from one vtable type to another. I think it'd be better to implement
> this function properly than to use macros (talk to Robert ;), especially
> considering that certain vt
Brent Dax wrote:
> > 2. What does having a Parrot_ prefix signify, considering
> > both the opcodes and the embed api use it?
>
> It signifies one of the following:
> -This function is externally visible.
> -This function belongs to Parrot at large, and not any particular
> subsystem (e.g. Par
IMHO, there's no way to find out quite like trying to use it :)
In my experiences with it thus far, it all seems to work fine. Melvin has
indicated that its API and internal structure may need some changes at
some point, but the basic functionality does seem to be there today, at
least enough
Brent,
Good stuff. Didn't you also send out a draft PDD about how types should
be named and managed in parrot at one point? I, for one, would love to
see a PDD that described C-level nanming and namespace management in
general.
--Josh
At 3:11 on 07/14/2002 PDT, "Brent Dax" <[EMAIL PROTECTE
I'm still catching up on backlogged mailing list mail here, but just to
try to be helpful-
Like many folks who lurk on this list, I have limited time to do detailed
work on parrot internals, much as I would like to.
But I am always excited when there's an opportunity to do simple, menial
task
I changed io.ops and pretty much the rest of parrot to always go through
PIO, which has streams. (or at least "handles").
I left core.ops alone because I didn't know what the intent was. Are those
ops meant to be superseded by the ones in io.ops?
IMHO, all IO in parrot should go through PIO, s
For file I/O (in core.ops, not io.ops), do we want to use file descriptors or streams?
open uses fopen(), close uses fclose(), but read uses read(), and write uses write().
And all the comments
say descriptors.
Any opinions one which way the code should be patched?
--
Bryan Logan
Foor for thought...
There currently is a 'morph' vtable entry, which I believe is intended to
morph from one vtable type to another. I think it'd be better to implement
this function properly than to use macros (talk to Robert ;), especially
considering that certain vtables might have special mor
Simon Wistow said:
> Might it be worth using something like
>
> http://usefulinc.com/chump/
>
> (as seen in use at http://pants.heddley.com/index.html)
> ?
>
> It's written in Python but there's a Perl replacement (to stem the PR
> nightmare), which is 99% complete, lurking around which
On Sun, Jul 14, 2002 at 08:54:30PM +0300, Iacob Alin said:
> The guys from London.pm wrote Scribot (http://www.scribot.com/) wich could
> be more useful...
Yeah I know - Leon wrote the original and then I patched it :)
http://thegestalt.org/simon/perl/scribot2.html
Leon's done another revision
# New Ticket Created by "Sean O'Rourke"
# Please include the string: [perl #814]
# in the subject line of all future correspondence about this issue.
# http://bugs6.perl.org/rt2/Ticket/Display.html?id=814 >
PerlString sets the PMC_is_buffer_ptr_FLAG flag in pmc->flags, but none of
the other
Stephen Rawls:
# I've only been involved with parrot since last week,
# but I've been learning quickly from all the
# documentation. With the recent activity about lack of
# documentation, I thought I'd try to help out as best I could.
# I've attached a file for an rx.dev candidate.
# Some
In message <[EMAIL PROTECTED]>
Melvin Smith <[EMAIL PROTECTED]> wrote:
> At 03:54 PM 7/14/2002 +0100, Tom Hughes wrote:
> >I've been trying to make sense of the current status of keyed access
> >at all levels, from the assembler through the ops to the vtables and
> >it has to be said th
Simon Wistow said:
> Might it be worth using something like
>
> http://usefulinc.com/chump/
>
> (as seen in use at http://pants.heddley.com/index.html)
> ?
>
> It's written in Python but there's a Perl replacement (to stem the PR
> nightmare), which is 99% complete, lurking around which was writte
At 03:54 PM 7/14/2002 +0100, Tom Hughes wrote:
>I've been trying to make sense of the current status of keyed access
>at all levels, from the assembler through the ops to the vtables and
>it has to be said that the harder I look the more confused I seem to
>become...
I think we all have...
FWIW,
Hello everyone,
I've only been involved with parrot since last week,
but I've been learning quickly from all the
documentation. With the recent activity about lack of
documentation, I thought I'd try to help out as best I
could. I've attached a file for an rx.dev candidate.
Some parts may be
At 9:36 PM -0500 7/13/02, Steve Purkis wrote:
>Hi,
>
>I was inspired by Time::HiRes to create 2 new simple ops for parrot:
>usleep(int), and sleep(num), to behave a bit more like the float version
>of the time op.
>
>I've attached a patch made off of the 0.0.6 source tree that works *for
>Linux* a
At 10:09 AM +0100 7/14/02, Simon Wistow wrote:
>On Sat, Jul 13, 2002 at 05:00:42PM -0400, Jim Cromie said:
>> can we could invent a super-lightweight markup language
>> that #parrot-eers would type into the stream to put meta-info into it ?
>
>Might it be worth using something like
>
>http://use
At 8:06 AM +0100 7/14/02, Leon Brocard wrote:
>Jim Cromie sent the following bits through the ether:
>
>> can we could invent a super-lightweight markup language
>> that #parrot-eers would type into the stream to put meta-info into it ?
>
>OK, I'll finally join this discussion. Yes, IRC is handy
# New Ticket Created by "Sean O'Rourke"
# Please include the string: [perl #813]
# in the subject line of all future correspondence about this issue.
# http://bugs6.perl.org/rt2/Ticket/Display.html?id=813 >
- updates IMCC to use keyed ops for spilling
- fixes a spelling error (n_spill vs. n
I've been trying to make sense of the current status of keyed access
at all levels, from the assembler through the ops to the vtables and
it has to be said that the harder I look the more confused I seem to
become...
It all seems to be a bit of a mess at the moment, and I'd like to have
a go at c
Ashley Winters:
# 1. Why is test_main.c not named main.c?
Because parrot.exe was originally named test_prog.exe, so at the time it
made sense for it to be called test_main.c.
# 2. What does having a Parrot_ prefix signify, considering
# both the opcodes and
# the embed api use it? It's hard to
On Sat, Jul 13, 2002 at 05:00:42PM -0400, Jim Cromie said:
> can we could invent a super-lightweight markup language
> that #parrot-eers would type into the stream to put meta-info into it ?
Might it be worth using something like
http://usefulinc.com/chump/
(as seen in use at http://pants.hedd
Hrm, I had intended to put my questions at the end. I hit Send early.
Questions:
1. Why is test_main.c not named main.c?
2. What does having a Parrot_ prefix signify, considering both the opcodes and
the embed api use it? It's hard to distinguish between them.
3. What source files implement wh
I'm trying to pay attention to the difficulties I have understanding parrot so
I can give some decent n00b feedback before I know the code like the back of
my hand.
First, test_main.c is a totally non-obvious location for parrot.exe's main().
I dismissed it out of hand when I did grep ^main. I
Hi,
I was inspired by Time::HiRes to create 2 new simple ops for parrot:
usleep(int), and sleep(num), to behave a bit more like the float version
of the time op.
I've attached a patch made off of the 0.0.6 source tree that works *for
Linux* as a proof of concept to try and spark some discussion.
38 matches
Mail list logo
