On Sunday 19 March 2006 10:58, Will Coleda wrote:
> in compilers/tge/TGE.pir, we have
>
> .sub '__onload' :load
> # use other modules
> load_bytecode 'compilers/tge/TGE/Rule.pir'
> load_bytecode 'compilers/tge/TGE/Instance.pir'
> load_bytecode "compilers/tge/TGE/Parser.pir"
>
>
On Sunday 19 March 2006 05:32, Bernhard Schmalhofer wrote:
> I tried to use something like:
>
> example_output_like( "examples/benchmarks/arriter.pir",
> $outputs{arriter.pit}, todo => 'syntax error' );
>
> However the 'todo' flag is not honored. My guess is that the TODO
> variable isn't set in
On Sat, Mar 18, 2006 at 11:01:34PM -0800, Allison Randal wrote:
> But, yes, I agree with the principle of not maintaining two
> completely separate implementations for synchronous and asynchronous
> ops. The earlier design approached that by having the synchronous ops
> be asynchronous inter
# New Ticket Created by Will Coleda
# Please include the string: [perl #38761]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38761 >
in compilers/tge/TGE.pir, we have
.sub '__onload' :load
# use other modules
l
On Sat, Mar 18, 2006 at 10:44:59AM -0800, [EMAIL PROTECTED] wrote:
> =item *
>
> -C returns a string representing a socket address, generated
> +C returns an object representing a socket address, generated
> from a port number (integer) and an address (string).
> +=head2 IPv6 Support
> +
> +T
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #38760]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38760 >
Hi,
I tried to use something like:
example_output_like( "examples/benchmarks
> "AR" == Allison Randal <[EMAIL PROTECTED]> writes:
AR> That interface is unnecessarily complex. But more importantly, the
AR> choice between async and sync is not set per filehandle, it's per
AR> operation. It could be very common to combine the two, such as
AR> using synchronous ope
