Carlin Bingham (via RT) wrote:
> This patch makes accept() return an instance of IO::Socket::INET with
> the $!PIO attribute set to the Parrot IO object that accept() currently
> returns.
>
> This will affect applications that currently call recv() from the object
> created
# New Ticket Created by Carlin Bingham
# Please include the string: [perl #70045]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=70045 >
The current IO::Socket::INET.accept() returns a Parrot IO object rather
than
We've replaced Parrot::IO::Capture::Mini throughout with
IO::CaptureOutput, so I'm removing Mini.pm from the distribution and
resolving the ticket. Thanks to Alan Rocker for assistance.
On Fri Dec 14 08:37:50 2007, [EMAIL PROTECTED] wrote:
> Unless someone shouts, in a few hours I'll be applying a patch visible
> here: http://thenceforward.net/parrot/diff.io.captureoutput.txt
Patches applied to trunk in r23890.
Unless someone shouts, in a few hours I'll be applying a patch visible
here: http://thenceforward.net/parrot/diff.io.captureoutput.txt
Am working on this with new Parrot contributor Alan Rocker. We've
transformed 17 tests so far; 65 to go.
by creating Parrot::IO::Capture::Mini. Its main use is to
capture verbose output during testing so as to reduce terminal
clutter and to see if correct output is generated.
I've run into a number of difficulties with P::IO::C::Mini and
tonight began to explore the possibility of replacing it w
"Vishal Soni" <[EMAIL PROTECTED]> wrote:
Is Parrot IO going to be implemented via opcodes or PMC?
I looked at some old email discussion. There were discussions on
refactoring
some IO opcodes to PMC's (e.g socket opcodes). Have we reached on any
decisions as to how we a
Hi,
Is Parrot IO going to be implemented via opcodes or PMC?
I looked at some old email discussion. There were discussions on refactoring
some IO opcodes to PMC's (e.g socket opcodes). Have we reached on any
decisions as to how we are going to implement the Parrot IO?
--
Thanks,
Vishal
On Sat, Dec 10, 2005 at 01:21:27PM -1000, Joshua Hoblitt wrote:
> On Sat, Dec 10, 2005 at 03:04:09PM -0800, chromatic wrote:
> > Seems reasonable to me, unless curdir() can ever return 0 or undef, and
> > also fixes my bug #37875.
>
> We could explicitly test if the return eq '' which would let 0
Awww, I bet you meant bug #37865. #37876 is clearly a duplicate so I'm
going to merge #37876 into #37865.
-J
--
On Sat, Dec 10, 2005 at 02:48:25PM -1000, Joshua Hoblitt wrote:
> On Sat, Dec 10, 2005 at 03:04:09PM -0800, chromatic wrote:
> > Seems reasonable to me, unless curdir() can ever return
On Sat, Dec 10, 2005 at 03:04:09PM -0800, chromatic wrote:
> Seems reasonable to me, unless curdir() can ever return 0 or undef, and
> also fixes my bug #37875.
It there something 'magical' about 37875? RT won't let me view it.
--
RT Error
No permission to view ticket
--
-J
--
pgpL6
On Sat, Dec 10, 2005 at 03:04:09PM -0800, chromatic wrote:
> On Sat, 2005-12-10 at 12:52 -1000, Joshua Hoblitt wrote:
>
> > I think we need to also change Parrot::IO::Directory->relative_path() to
> > filter out '' and replace it with '.' or else we'
On Sat, 2005-12-10 at 12:52 -1000, Joshua Hoblitt wrote:
> I think we need to also change Parrot::IO::Directory->relative_path() to
> filter out '' and replace it with '.' or else we'll have to bundle a
> recent version of File::Spec with Parrot, which I&#
- abs2rel() used to return the empty string when its two arguments
> >were identical, which made no sense. Now it returns
> >curdir(). [Spotted by David Golden]
> >
> >So, maybe we should replace '.' by File::Spec->curdir() but I'm not sure.
>
>
# New Ticket Created by Alberto Manuel Brandao Simoes
# Please include the string: [perl #37876]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37876 >
---
osname= darwin
osvers= 8.0
arch= darwin-thread-multi-2level
cc=
arrotbug regarding:
"Bug with Parrot::IO test"
There is no need to reply to this message right now. Your ticket has been
assigned an ID of [perl #37876].
Please include the string:
[perl #37876]
In the subject line of all future correspondence about this issue. To do so,
y
replace '.' by File::Spec->curdir() but I'm not sure.
Alberto
Parrot Assembler via RT wrote:
Greetings,
This message has been automatically generated in response to the
creation of a parrotbug regarding:
"Bug with Parrot::IO test"
There is no need to reply to t
> [EMAIL PROTECTED] - Mon Jun 30 07:15:44 2003]:
>
>
> A further data point: the tests pass if I use IMCC to assemble them,
> rather than assemble.pl
>
> Simon
>
Since assemble.pl is no more, closing this ticket.
At 09:16 AM 10/31/2003 -0500, David Robins wrote:
On Thu, 30 Oct 2003, Melvin Smith wrote:
> At 12:09 AM 10/31/2003 +, Nicholas Clark wrote:
> >On Thu, Oct 30, 2003 at 01:54:24AM -0500, Melvin Smith wrote:
> > > Parrot fetched its first web page tonight. Its a baby step, but
hey... :)
> >
> >
On Thu, 30 Oct 2003, Melvin Smith wrote:
> At 12:09 AM 10/31/2003 +, Nicholas Clark wrote:
> >On Thu, Oct 30, 2003 at 01:54:24AM -0500, Melvin Smith wrote:
> > > Parrot fetched its first web page tonight. Its a baby step, but hey... :)
> >
> >Can we do IPv6?
>
> Some of the changes are pretty
At 12:09 AM 10/31/2003 +, Nicholas Clark wrote:
On Thu, Oct 30, 2003 at 01:54:24AM -0500, Melvin Smith wrote:
> Parrot fetched its first web page tonight. Its a baby step, but hey... :)
>
> You can now stuff hostnames into a socket as well as a numeric IP address.
>
> see examples/io/http.imc
C
On Fri, Oct 31, 2003 at 12:09:14AM +, Nicholas Clark wrote:
> On Thu, Oct 30, 2003 at 01:54:24AM -0500, Melvin Smith wrote:
> > Parrot fetched its first web page tonight. Its a baby step, but hey... :)
I forgot to say:
Hey, cool! Nice work.
Today web pages, tomorrow self propagating worms? M
On Thu, Oct 30, 2003 at 01:54:24AM -0500, Melvin Smith wrote:
> Parrot fetched its first web page tonight. Its a baby step, but hey... :)
>
> You can now stuff hostnames into a socket as well as a numeric IP address.
>
> see examples/io/http.imc
Can we do IPv6?
(Not meant to be a throw away que
Parrot fetched its first web page tonight. Its a baby step, but hey... :)
You can now stuff hostnames into a socket as well as a numeric IP address.
see examples/io/http.imc
-Melvin
Melvin Smith <[EMAIL PROTECTED]> writes:
> >Did you consider using the method interface in ParrotIO? That ought to
> >be even extensible with user code.
>
> Yes, I'm trying to get back up to speed on everything. The method interface
> is a new feature that I need to look at.
I've written a first
At 09:59 AM 10/11/2003 +0200, Leopold Toetsch wrote:
Melvin Smith <[EMAIL PROTECTED]> wrote:
> I personally don't like to add an opcode for every special case
> because most of them are very rarely used, but as usual its
> up for discussion.
Did you consider using the method interface in ParrotIO?
Melvin Smith <[EMAIL PROTECTED]> wrote:
> I personally don't like to add an opcode for every special case
> because most of them are very rarely used, but as usual its
> up for discussion.
Did you consider using the method interface in ParrotIO? That ought to
be even extensible with user code.
>
At 11:23 PM 10/10/2003 +0100, Nicholas Clark wrote:
On Fri, Oct 10, 2003 at 05:55:11PM -0400, Melvin Smith wrote:
> Which ones? The PIOCTL ones are, for a lack of current
> interface, a way for interfacing to the lower level IO
> system through a catchall opcode. It can be anything from
> setting t
On Fri, Oct 10, 2003 at 05:55:11PM -0400, Melvin Smith wrote:
> Which ones? The PIOCTL ones are, for a lack of current
> interface, a way for interfacing to the lower level IO
> system through a catchall opcode. It can be anything from
> setting terminal modes, buffering, separator characters, the
Which ones? The PIOCTL ones are, for a lack of current
interface, a way for interfacing to the lower level IO
system through a catchall opcode. It can be anything from
setting terminal modes, buffering, separator characters, the
list goes on.
Although we probably want to make separate ops for
commo
On Fri, Oct 10, 2003 at 02:43:10AM -, Melvin Smith wrote:
> +else if(arg == PIOCTL_BLKBUF) {
> + PIO_setbuf(interpreter, pmc, PIO_UNBOUND);
> + return 0;
> +}
> +else return -3;
> case PIOCTL_CMDGETBUFSIZE:
>
Clinton Pierce wrote:
What I do know is that imcc -t under Win32 is crash-happy
Snippet runs fine on Linux (with typo adjusted or not) as well as your
previous one, -t or not.
But, as IO is under *construction* some issues might remain. They'll get
resolved.
leo
Typo!
> getstderr P3 # STDOUT
Should have been "getstdout"
Although... if left at getstderr the error also goes away. (Add that to my bullet
list.) My haven't-grokked-the-code psychic abilities tell me that "getstdout" does
something Real Bad to the stdout filehandle
I'm not sure whether getstd\w+ is supposed to give me a new reference or not. From
now on I'll code that portion defensively.
What I do know is that imcc -t under Win32 is crash-happy and I can't trace beyond the
first getstdin. Greatly simplified example:
.sub _main
$P0=new PerlArray
"Clinton Pierce" <[EMAIL PROTECTED]> writes:
> Given that, there's a possible bug in Jürgen's patch (or IMCC?). Given:
>
> .sub _main
> call _INIT
> .arg 0
> call _READLINE
> .result $S0
> print $S0
> end
> .end
> .sub _INIT
> $P0=new PerlArray # A
Clinton Pierce wrote:
new $P4, PerlArray
A current workaround for the missing clone in ParrotIO:
getstdin P0
getstdout P1
getstderr P2
$P4[0], P0
$P4[1], P1
$P4[2], P2
leo
Clinton Pierce wrote:
set P1[0], P0
getstdout P0# <-- bug is here? Overwrote my P0.
set P1[1], P0
Yep a bug is here. But this bug is a BASIC compiler bug. Things that go
into aggregates (or are stored in lex pads/global tables) are stored by
reference. You
>>> .sub _main
>>> fdopen $P1, 0, "r" # STDIN
>
>BTW
> fdopen $P1, 0, "<" # read STDIN
>
>>> 3. its currently only defined for PIO_OS_UNIX
>
>> Okaaay, so the plan is for this to work and I should probably code this way anyway,
>> right?
>
> You could just
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Simon Glover <[EMAIL PROTECTED]> wrote:
> > I'm getting failures in tests 1 & 2 in t/pmc/io.t; however, both tests
> > seem to run fine if I run them in the debugger.
>
> valgrind does indicate, that there are unitialized items in many
> parts of io
Simon Glover <[EMAIL PROTECTED]> wrote:
> I'm getting failures in tests 1 & 2 in t/pmc/io.t; however, both tests
> seem to run fine if I run them in the debugger.
valgrind does indicate, that there are unitialized items in many
parts of io_buf.c.
(I don't know, if these tests even should use the
A further data point: the tests pass if I use IMCC to assemble them,
rather than assemble.pl
Simon
# New Ticket Created by Simon Glover
# Please include the string: [perl #22857]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=22857 >
Hi,
I'm getting failures in tests 1 & 2 in t/pmc/io.t; however, both tests
seem to
Clinton Pierce <[EMAIL PROTECTED]> wrote:
>> .sub _main
>> fdopen $P1, 0, "r" # STDIN
BTW
fdopen $P1, 0, "<" # read STDIN
>> 3. its currently only defined for PIO_OS_UNIX
> Okaaay, so the plan is for this to work and I should probably code this way anyway
> First, always check the result of IO operations. If something fails,
> these return a PerlUndef, so:
> .sub _main
> fdopen $P1, 0, "r" # STDIN
> defined $I0, $P1
*Doh* Stupid Newbie Error.
> unless $I0, err
> read $S0, $P1, 255
>
Clinton A. Pierce (via RT) wrote:
Suggestions welcome!
First, always check the result of IO operations. If something fails,
these return a PerlUndef, so:
.sub _main
fdopen $P1, 0, "r" # STDIN
defined $I0, $P1
unless $I0, err
read $S0, $P1, 255
print $S0
# New Ticket Created by "Clinton A. Pierce"
# Please include the string: [perl #22854]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=22854 >
This is either an oversight in the current implementation *or* its a bug. Or bot
@@
>v = op_assembly[*pc].string_register_address;
>for (i = 0; i < v.amount; i++)
>{
> -address = (INTVAL
> *)&interpreter->string_reg->registers[pc[v.info[i].number]];
>
48 matches
Mail list logo
