On 3/5/06, Chris Dolan <[EMAIL PROTECTED]> wrote:
> On Mar 5, 2006, at 3:55 PM, David Wheeler wrote:
>
> > On Mar 5, 2006, at 13:52, Chris Dolan wrote:
> >
> >> Advice? While this example is contrived, the "eval
> >> { require ... }" idiom is used often in the wild, so this is not a
> >> wholly un
I finally got around to writing up a patch to parrot that would allow
the features I mentioned a while back. There aren't any heuristics,
just braces. The first file is a patch to imcc.l and imclexer.c(may as
well). The second file is a set of macro's I've already written up(not
documented p
Chris Dolan writes:
> The problem is that I don't know how to distinguish between a load
> failure or a compile failure.
In this particular case you can get the failure by removing Bar from
%INC before checking that it loads:
use_ok('Foo');
delete $INC{'Bar.pm'};
use_ok('Bar');
In general
Chris Dolan wrote:
Advice? While this example is contrived, the "eval { require ... }"
idiom is used often in the wild, so this is not a wholly unrealistic
scenario.
Real-world example. SVN::Web uses this idiom to determine whether to
use CGI or CGI::Fast.
Even if CGI::Fast is installed i
On Mar 3, 2006, at 20:27, Allison Randal wrote:
We're going to try something a little different. With Chip's blessing
I've written a very early draft of the PDD for I/O (not numbered yet).
The attached PDD isn't a completed document with Chip's seal of
approval, it's a seed for discussion.
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
getpeername/getsockname
getsockopt/setsockopt
I'd view shutdown as most important, as I believe that there are some
protocols you can't i
Matisse Enzer wrote:
Currently we are evaluating these options:
1) Maintain a list of the .tar.gz files and install from CPAN,
for example M/MA/MATISSE/Text-TagTemplate-1.8.tar.gz
2) Put the CPAN .tar.gz files in a local CPAN repository and use
CPAN::Site to install - that way we
I've adjusted call argument bits according to r11754 (pdd03). This means
that all PASM code that is using function calls *and* any of (slurpy,
flatten, optional, or named arguments) has to be adjusted. These bits
need shifting left by 2.
PIR code is working unaltered.
Sorry for the
On Mar 6, 2006, at 6:08 AM, Leopold Toetsch wrote:
Using opcodes for all the IO has some disadvantages:
a) namespace pollution: all opcodes are reserved words in Parrot
b) opcodes aren't overridable, that is you can't provide your own
'print' opcode for e.g. debugging
c) all such IO opcodes ha
On 2006-03-05, Michael Peters <[EMAIL PROTECTED]> wrote:
>
>
> Yuval Kogman wrote:
>> On Sat, Mar 04, 2006 at 09:09:00 -0500, Michael Peters wrote:
>>> It's very similar in nature to the Pugs smoke test server, but is completely
>>> project agnostic. It's also completely self contained (contains lo
(This message is targeted at the Test::WWW::Selenium maintainers, but I
think the response will be of interest to others here ).
I've got a test suite built with Selenium, but I would like to the
output in TAP to centralize the reporting, perhaps using Smolder once I
Smolder installed.
It appear
On Mar 6, 2006, at 4:10 AM, Nik Clayton wrote:
Matisse Enzer wrote:
Currently we are evaluating these options:
1) Maintain a list of the .tar.gz files and install from CPAN,
for example M/MA/MATISSE/Text-TagTemplate-1.8.tar.gz
2) Put the CPAN .tar.gz files in a local CPAN repository a
Matisse Enzer wrote:
>
> On Mar 5, 2006, at 3:15 PM, Michael Peters wrote:
>>
>> Matisse Enzer wrote:
>>> After some trouble, I managed to create a distribution tarball for my
>>> patched Redhat 8 system from smolder-0.01-src using
>>> bin/smolder_makedist.
>>
>> Thanks for trying this out so so
On Mar 5, 2006, at 15:35, chromatic wrote:
On Sunday 05 March 2006 11:46, Nicholas Clark wrote:
On Fri, Mar 03, 2006 at 11:27:05AM -0800, Allison Randal wrote:
[It's worth considering making all the network I/O opcodes use a
consistent way of marking errors. At the moment, all return an
"Leopold Toetsch" <[EMAIL PROTECTED]> wrote:
* opcode vs function / method
open P0, "data.txt", ">"
print P0, "sample data\n"
Using opcodes for all the IO has some disadvantages:
a) namespace pollution: all opcodes are reserved words in Parrot
b) opcodes aren't overrida
On Mar 6, 2006, at 23:16, Jonathan Worthington wrote:
"Leopold Toetsch" <[EMAIL PROTECTED]> wrote:
$I0 = pio.'print'("sample data\n") # return sucess (>=0) or
failure (<0)
pio.'print'("sample data\n") # throw exception on failure
Could perhaps get fun for compilers though
On Mar 6, 2006, at 4:08, Leopold Toetsch wrote:
Some remarks re the pdd and discussion so far.
o "write" ... [Is this redundant?]
"write" isn't needed. It is there, as some time ago, "print" was't
able to write strings with "\0"s inside.
Now marked in the PDD as deprecated.
(To make
On Mar 6, 2006, at 5:31 PM, Allison Randal wrote:
On Mar 6, 2006, at 4:08, Leopold Toetsch wrote:
* opcode vs function / method
open P0, "data.txt", ">"
print P0, "sample data\n"
Using opcodes for all the IO has some disadvantages:
a) namespace pollution: all opcodes
On Mar 7, 2006, at 0:31, Allison Randal wrote:
It's overkill to require people to write:
P0 = getstdout
P0.'print'(S1)
Yep. The more that printing to stdout is heavily used in the test
suite. OTOH opcode vs method is merely a matter of what the assembler
is creating. That is: there are 2 n
On Mar 5, 2006, at 13:52, Joshua Isom wrote:
On Mar 5, 2006, at 3:46 PM, Nicholas Clark wrote:
On Sun, Mar 05, 2006 at 02:53:29PM -0600, Joshua Isom wrote:
A pasm include, such as the signal.pasm(even though signals don't
work
yet), would suffice and is generated at compile time. Parsing .h
On Mar 7, 2006, at 0:31, Allison Randal wrote:
pio = socket(".AF_UNIX", ...)
It seems like a more general problem than that. Like, you want a way
of flagging a constant when you define it as to whether it should be
substituted when compiling to bytecode or substituted when
interpreting t
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Tue, 7 Mar 2006 00:11:13 +0100
On Mar 6, 2006, at 23:16, Jonathan Worthington wrote:
> "Leopold Toetsch" <[EMAIL PROTECTED]> wrote:
>> $I0 = pio.'print'("sample data\n") # return sucess (>=0) or
>> failure (<0)
>> pio.
22 matches
Mail list logo
