I have a question on your test suite.
Would backticks not be more portable then trying to figure out how to
redirect STDOUT on each OS? To me, it would just be simpler to use the
--ouput flag of the assembler to create the .pbc file, and then use
backticks to capture the output of the interpreter.
-----Original Message-----
From: Mattia Barbon
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: 9/14/2001 4:03 PM
Subject: [PATCH] testsuite and Win32 compilation
> PLEASE can someone rewrite the tests to actually *test* things
> and print "ok 1\n" and so on?
Here it is ( for the second time )
> Quick, or I'll call Schwern in.
Ah, I thought you missed my patches, then I was correct
both attached
testsuite.diff:
-----------------------------
Run with
perl -Mlib=lib t/harness
just as make test in perl5
Tests live in t/*/*.t .
In case of failure the assembler, bytecode and output
are available as t/dir/testnnn.pasm/pbc/out
-------------------------------
things.diff
---------------------------------
This patch adds:
an hints directory ( files are named hints/lc($^O).pl )
therir contents are eval'd in Config.pl
it adds to Config.pl some flags
--debugging Enable debugging
adds -g or equivalento to compiler flags
--defaults Accept all default values
like -d option to perl5 Configure
--define name=value Defines value name as value
i.e --define cc=gcc --define ld=myld
--help This text
--version Show assembler version
Win32 does not have mmap() ( it has memory mapped files, but with
a different API, so I just read() the bytecode in a malloc()ed
buffer.
Compilation tested on Win32 (MSVC5 and MinGW ) and Linux
--------------------------------
Best regards
Mattia
P.S.: what should I do to make patches stand out better
in the mailing list?
<<Attachment information.>> <<things.diff>> <<Text from file
'testsuite.diff'>>
