[perl #24371] [PATCH] Unescaped metachars in output_like tests

2003-10-31 Thread via RT
# New Ticket Created by  Adam Thomason 
# Please include the string:  [perl #24371]
# in the subject line of all future correspondence about this issue. 
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24371 


A few tests using output_like and friends have unescaped '.' chars.  These aren't 
causing or misreporting failures now, but could possibly trigger false negatives 
later.  The attached patch fixes them.

--
Adam Thomason
[EMAIL PROTECTED]



-- attachment  1 --
url: http://rt.perl.org/rt2/attach/66770/49892/9da58c/testmeta.patch



testmeta.patch
Description: testmeta.patch


Re: [PS] open patches

2003-10-31 Thread Michael Scott
Reeducation succeeded.

I resolved #24030 and #24038 by changing the Status field and hitting 
Save Changes, then I noticed there was a Resolve option on the top 
righthand side which asks for details for a notification email. I'm 
wondering which is the approved way?

I ask because I'll add a details to the ParrotSubmissions page on the 
wiki when I'm done.

	http://www.vendian.org/parrot/wiki/bin/view.cgi/Main/ParrotSubmissions

BTW I submitted a pod version of this page as #24103 with a suggestion 
for a [NEW] prefix convention for new files but it got warnocked.

Mike

On 31 Oct 2003, at 05:16, Robert Spier wrote:

My account (mikescott) at http://auth.perl.org/auth/account shows the
correct email. The RT page assures me that I'm signed in as mikescott.
I go to the Modify ticket #24030 and set Status to resolved, click 
Save
Changes and get Status: Permission Denied.
RT had a different idea of what your email address was.  (There is an
issue with propagation.) I've reeducated it.
Try now.

-R




[perl #24376] [PATCH] NetBSD

2003-10-31 Thread via RT
# New Ticket Created by  Nick Kostirya 
# Please include the string:  [perl #24376]
# in the subject line of all future correspondence about this issue. 
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24376 


Hello.

With this patch Parrot is being successfully built on NetBSD 1.6.

Nick.

P.S.

perl t/harness --gc-debug --running-make-test  -b t/op/*.t t/pmc/*.t
t/native_pbc/*.t

All tests successful, 27 subtests skipped.

perl t/harness
...
All tests successful, 4 subtests skipped.

perl t/harness t/src/*.t

Failed Test  Stat Wstat Total Fail  Failed  List of Failed

---
t/src/manifest.t1   256 41  25.00%  4
3 subtests skipped.
Failed 1/9 test scripts, 88.89% okay. 1/59 subtests failed, 98.31% okay.


-- attachment  1 --
url: http://rt.perl.org/rt2/attach/66867/49915/aa7b90/exec.h.patch



exec.h.patch
Description: exec.h.patch


[perl #24378] [PATCH] fix warnings in cpu_deps.c on Solaris

2003-10-31 Thread via RT
# New Ticket Created by  David Robins 
# Please include the string:  [perl #24378]
# in the subject line of all future correspondence about this issue. 
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24378 


In a clean build from latest CVS sources, I get:

src/cpu_dep.c
src/cpu_dep.c, line 36: warning: initializer does not fit or is out of
range: 0x91d02003
src/cpu_dep.c, line 38: warning: initializer does not fit or is out of
range: 0x81c3e008

The patch changes the type that stores the instruction from int to unsigned
int.

HTH,

-- 
Dave
Isa. 40:31


-- attachment  1 --
url: http://rt.perl.org/rt2/attach/66873/49921/067741/parrot-Solaris-cpu_dep.patch

--- cpu_dep.old 2003-10-31 09:25:24.937817000 -0600
+++ cpu_dep.c   2003-10-31 09:26:00.612197000 -0600
@@ -27,7 +27,7 @@
 {
 #if defined(__sparc) /* Flush register windows */
 static union {
-   int insns[4];
+   unsigned int insns[4];
 double align_hack[2];
 } u = { {
 #  ifdef __sparcv9



Re: Parrot IO fun

2003-10-31 Thread David Robins
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?
snip

 Some of the changes are pretty simple (like instead of using inet_addr, use
 inet_aton, etc.) while I'll not sure about the rest. It's been a while
 since I did any socket projects but its all coming back pretty fast. :)

Speaking of which, (this version of) Solaris needs -lresolv to use inet_aton;
uname -a:

SunOS foobar 5.8 Generic_108528-10 sun4u sparc SUNW,Ultra-4

The error:

cc -o parrot -L/opt/SUNWspro/WS6/lib   -g imcc/main.o blib/lib/libparrot.a
-lsocket -lnsl -ldl -lm
ild: the archive blib/lib/libparrot.a has entries with the same name --
consistency checks during incremental links are not possible for these
entries
ild: (undefined symbol) inet_aton -- referenced in the text segment of
blib/lib/libparrot.a(io_unix.o)
*** Error code 5
make: Fatal error: Command failed for target `parrot'

No error if I manually add -lresolv to C_LIBS in the Makefile.

-- 
Dave
Isa. 40:31



Re: Parrot IO fun

2003-10-31 Thread Melvin Smith
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... :)
 
 Can we do IPv6?
snip

 Some of the changes are pretty simple (like instead of using inet_addr, use
 inet_aton, etc.) while I'll not sure about the rest. It's been a while
 since I did any socket projects but its all coming back pretty fast. :)

Speaking of which, (this version of) Solaris needs -lresolv to use inet_aton;
uname -a:
SunOS foobar 5.8 Generic_108528-10 sun4u sparc SUNW,Ultra-4
Thanks for the report. I'll patch it. Time for be to get my old Sun box out of
the closet.
-Melvin




Re: Parrot 0.0.13 Screaming Pumpkin Released!

2003-10-31 Thread Leopold Toetsch
While not totally through it, I'm currently making good progress in
following release instruction's 10a). Thanks to Steve to put that file
together, it went all smoothly.
I hope that all announces got it to their recipients and that everything
is working fine.

Have fun,
leo, going tonight zum Heurigen Striezelpaschen


[perl #24381] Parrot doesn't build with PIO_OS_STDIO defined

2003-10-31 Thread via RT
# New Ticket Created by  Simon Glover 
# Please include the string:  [perl #24381]
# in the subject line of all future correspondence about this issue. 
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24381 



 An attempt to build Parrot with PIO_OS_STDIO defined (as is the case
 when you're trying to build miniparrot) dies in core_ops.c with the error
 message:

  ops/io.ops: In function `Parrot_sockaddr_s_i_s':
  ops/io.ops:497: parse error before `;'
  [etc...]
 
 The reason is the interaction between the sockaddr op definition:

  op sockaddr(out STR, in INT, in STR) {
$1 = PIO_sockaddr_in(interpreter, (unsigned short)$2, $3);
goto NEXT();
  }

 and this ifdef in io.h:

#ifdef PIO_OS_STDIO
extern INTVAL   PIO_stdio_isatty(PIOHANDLE fd);
extern INTVAL   PIO_stdio_getblksize(PIOHANDLE fd);
#  define PIO_isatty(x)   PIO_stdio_isatty(x)
#  define PIO_sockaddr_in(i,p,a)
#  define PIO_getblksize(x)   PIO_stdio_getblksize(x)
#endif

 The preprocessor turns the op definition into:

   op sockaddr(out STR, in INT, in STR) {
$1 = ;
goto NEXT();
  }   

 which is clearly a syntax error. 

 An easy fix is to wrap the offending line in #ifndef PIO_OS_STDIO .. 
 #endif, but there may be a better solution.

 Regards,
 Simon






Re: [PS] open patches

2003-10-31 Thread Robert Spier
 I resolved #24030 and #24038 by changing the Status field and hitting 
 Save Changes, then I noticed there was a Resolve option on the top 
 righthand side which asks for details for a notification email. I'm 
 wondering which is the approved way?

Either is fine.  By default the Resolve page will only add a comment
unless you change it to Correspondence.  But if you don't enter any
text in the big box, none will be recorded.  

-R



Re: cvs commit: parrot/examples/io http.imc

2003-10-31 Thread Josh Wilmes

Very cute!

However, i'm curious about the choice of interface.   Having individual
ops for something like a socket API seems rather peculiar to me.  

Why do we not have an object oriented interface on a socket class?

(ditto for non-trivial file IO)

--Josh


At 6:45 on 10/30/2003 GMT, Melvin Smith [EMAIL PROTECTED] wrote:

 cvsuser 03/10/29 22:45:05
 
   Added:   examples/io http.imc
   Log:
   Sample to grab a home page through HTTP.
   
   Revision  ChangesPath
   1.1  parrot/examples/io/http.imc
   
   Index: http.imc
   ===
   # http client, connects to WWW port and grabs a page. 
   # Be sure to set PARROT_NET_DEVEL to 1 in io/io_private.h
   # and rebuld Parrot or the network layer won't exist
   
   .sub _main
   .local pmc sock
   .local string address
   .local string buf
   .local int ret
   .local int len
   print Creating socket.\n
   # create the socket handle 
   socket sock, 2, 1, 0
   unless sock goto ERR
   # Pack a sockaddr_in structure with IP and port
   #sockaddr address, 80, 129.42.18.99
   sockaddr address, 80, www.ibm.com
   print Connecting to http://www.parrotcode.org:80\n;
   connect ret, sock, address 
   print connect returned 
   print ret 
   print \n
   send ret, sock, GET /us/ HTTP/1.0\nUser-agent: Parrot\n\n 
   poll ret, sock, 1, 5, 0
   MORE:
   recv ret, sock, buf 
   if ret  0 goto END
   print buf 
   goto MORE 
   ERR:
   print Socket error\n
   end
   END:
   close sock 
   end
   .end
   
   
   
   




Re: cvs commit: parrot/examples/io http.imc

2003-10-31 Thread Melvin Smith
At 07:34 PM 10/31/2003 -0500, Josh Wilmes wrote:

Very cute!

However, i'm curious about the choice of interface.   Having individual
ops for something like a socket API seems rather peculiar to me.
Why do we not have an object oriented interface on a socket class?

(ditto for non-trivial file IO)
I arrived at the same conclusion but I wanted something to
play with for now. It just isn't elegant to have opcodes for things like
sockets and extended IO APIs.
I'm going to put my effort towards the class/object internals and
imcc for a bit, then I plan to convert all of the IO API to methods
(not just the socket API). But, there is no reason we can't leave
a few common calls exposed as opcodes (open, close, print, etc.)
You make a good point though. Do not consider what I've done
for IO to be the official API going forward. There were a lot of
things written before objects (and even PMCs) that are just
temporary.
-Melvin




Parrot 0.0.13 Screaming Pumpkin Released!

2003-10-31 Thread Leopold Toetsch
  Parrot 0.0.13 Screaming Pumpkin Released!

Your new Bluza[1] proudly presents Parrot 0.0.13 Halloween edition[2].
Proposed originally as a fun release it has a remarkable list of
improvements, additions, and fixes[3].
While not really milestones are reached, many steps towards these are
done.
After some pause you can grab it from
http://www.cpan.org/authors/id/L/LT/LTOETSCH/parrot-0.0.13.tar.gz
or just get the latest and best from CVS by following the directions at
http://dev.perl.org/cvs/.
Turn your web browser towards http://www.parrotcode.org/ for more
information about Parrot, get involved, and:
Have fun!
leo
[1] Austrian dialect word for pumpkin with some aftermath of an head
filled with water.
[2] Version number fits nicely todays date - and we don't release
by the dozen.
[3] The list of changes includes:

- The Big Move: Parrot source and build files rearranged into sub dirs
- Build imcc as parrot
- Objects more finished
- Delegate vtable methods to byte code
- Binary multi-method dispatching
- Isa and does methods for PMCs
- Call byte code from C
- Start of extension interface
- Experimental struct handling
- Catch access to NULL PMCs
- Experimental network socket interface code and opcodes
- IO fixes and improvements
- Dynamic opcode libraries
- Fix-assigned opcode numbers
- Argument flattening for function calls
- More native call interface (NCI) signatures
- Ncurses, postgres, and pcre interface libraries
- Forth language is vastly improved
- New tcl and urm languages
- BSD and Win32 build improvements
- Many new tests and fixes