Simon Cozens writes:
> Any progress on this? I'd like to start drawing up something for the
> internal variables API soonish. Well, last month, actually, but soonish
> would do just fine. :)
[EMAIL PROTECTED] writes:
>> Simon,
>> Here (finally) is that list of SV functions. I ran out of time t
Simon,
Here (finally) is that list of SV functions. I ran out of time to
trawl through the pp*.c files, so this is based only on what I found
in sv.c.
Dave M.
This a grouping and summary of the functions in sv.c (ignoring the
strictly local ones). The grouping scheme is probably a bit arbitrar
On Mon, Jun 11, 2001 at 11:32:33AM +0100, Dave Mitchell wrote:
> I'm about 3/4 the way through sv.c - I estimate another week before I'm
> done. The positive side effect is an impending patch that will add 500+
> lines of comments to sv.c.
Very cool! Thanks very much indeed.
--
You are in a maz
Simon Cozens <[EMAIL PROTECTED]> wrote:
> On Wed, May 23, 2001 at 06:08:52PM +0100, Simon Cozens wrote:
> > ACY's taking a look into this too, so you may want to co-ordinate to avoid
> > clashing. I've also told him what I'd like: something like this:
> >
> > Scalar
> > Strings
> > Ch
On Wed, May 23, 2001 at 06:08:52PM +0100, Simon Cozens wrote:
> ACY's taking a look into this too, so you may want to co-ordinate to avoid
> clashing. I've also told him what I'd like: something like this:
>
> Scalar
> Strings
> Chop from beginning
> Format a la sprintf
>
On Thu, May 24, 2001 at 03:12:03PM +0100, Dave Mitchell wrote:
> Are you also interested in functions on scalars that happen to be in pp*.c
> rather than sv.c?
Definitely; I want an idea of what Perl 5 expects to be able to do with
scalars and aggregates so that I know what Perl 6 ought to expect
A. C. Yardley" <[EMAIL PROTECTED]> wrote:
>How about you take sv.c? And I'll take av.c and hv.c? Sound good?
okay, its a deal!
Simon Cozens <[EMAIL PROTECTED]> wrote:
> ACY's taking a look into this too, so you may want to co-ordinate to avoid
> clashing. I've also told him what I'd like: some
Dave Mitchell writes:
>> I've been meaning for a while to sit down and thoroughly go through sv.c
>> to understand and document it. So, consider sv.c 'grabbed'; if no-one's
>> done av.c and sv.c in the meantime, I may get round to them too.
> ^
> hv.c of course.
D
On Wed, May 23, 2001 at 06:04:17PM +0100, Dave Mitchell wrote:
> > I've been meaning for a while to sit down and thoroughly go through sv.c
> > to understand and document it. So, consider sv.c 'grabbed'; if no-one's
> > done av.c and sv.c in the meantime, I may get round to them too.
>
> I've been meaning for a while to sit down and thoroughly go through sv.c
> to understand and document it. So, consider sv.c 'grabbed'; if no-one's
> done av.c and sv.c in the meantime, I may get round to them too.
^
hv.c of course.
> If anyone wants to do some really useful work, they can scout through
> sv.c, av.c and hv.c, and summarise the functions that Perl 5 expects to
> be able to perform on scalars, arrays and hashes.
I've been meaning for a while to sit down and thoroughly go through sv.c
to understand and document
On Mon, May 21, 2001 at 05:43:28PM -0600, Nathan Torkington wrote:
> Not to speak for Dan, but there's no code yet to review or learn from.
> I'd love to see someone set up a perl *5* apprentice program, and
> Mark-Jason Dominus has some ideas on how it might work. For perl6,
> though, we're not
Not to speak for Dan, but there's no code yet to review or learn from.
I'd love to see someone set up a perl *5* apprentice program, and
Mark-Jason Dominus has some ideas on how it might work. For perl6,
though, we're not yet at a place where I think it makes sense. Right
now there's so little d
Ok, the idea of a master-apprentice program, where the wannabes,
while working with masters, sort-of cut their teeth on the docs, and
then move up in skills over time, has been mentioned a few times on
this list and discussed rather extensively on perl6-meta. Now, I'm
wondering, has a consensus o
14 matches
Mail list logo
