Author: pmichaud
Date: Thu Mar 16 18:44:22 2006
New Revision: 11914
Modified:
trunk/docs/pdds/pdd03_calling_conventions.pod
Log:
"Paramters" -> "Parameters"
Modified: trunk/docs/pdds/pdd03_calling_conventions.pod
==
Just a quick note that in r11916 I've updated PGE's
internal attribute names to match the new secondary
sigils identified by S12. Thus, @:capt is now @!capt,
&:corou is now &!corou, etc.
(For the pugs folks, I updated the Hs.pir file as well.)
This shouldn't have much of an impact on anyone usi
Fixed, finally.
On Mar 16, 2006, at 5:40 AM, Alberto Simoes wrote:
Cheers
Alberto
On Mar 11, 2006, at 2:07, Nicholas Clark wrote:
I feel more comfortable with the idea of IO being methods on PMCs
than raw
OPs.
They are methods on I/O objects internally. (Just as most opcodes on
PMCs actually call vtable methods.) So, the question isn't as
significant as it appears. I
I've just applied a change (r11921) to PGE that allows
embedded closures in rules to designate a "return value" for
a match (recently added to S05).
Essentially this means that a rule such as
/:lang(PIR) foo {{ .return "bar" }} /
will match a string containing "foo" but gives the returned ma
On Mar 3, 2006, at 15:54, Joshua Isom wrote:
Concerning all the byte/character issues, all the string opcodes
except bytelength work with characters. But the io subsystem
currently only deals with bytes. I know there is the speed issue
for things like reading with dealing with utf8, but
On Fri, Mar 17, 2006 at 07:08:55PM -0600, Patrick R. Michaud wrote:
> I've just applied a change (r11921) to PGE that allows
> embedded closures in rules to designate a "return value" for
> a match (recently added to S05).
> [...]
I neglected to mention in my previous post that this update
seems t
On Mar 6, 2006, at 4:06, Nicholas Clark wrote:
On Fri, Mar 03, 2006 at 11:27:05AM -0800, Allison Randal wrote:
=head2 Network I/O Opcodes
Functionality wise, the following are missing:
shutdown
Added.
getpeername/getsockname
getsockopt/setsockopt
These seem rare, and intimatel
I just committed a more complete draft of the I/O PDD to docs/pdds/
clip/pddXX_io.pod. I've integrated or responded to the mailing list
comments. I also added a good bit of additional discussion of
asynchronous operations and error handling. The original draft was
"how it works now", while t
