My unanswered question below was legitimate, but if you insist...
Perhaps another register can hold the number of problems
with this calling convention.
>Dan Sugalski wrote:
>> 1) The changes I proposed are going in. We get arg counts for I/S/N
>> registers if they're used.
>
>What purpose
I would suggest something along the lines of:
&like_html(actual_value, expected_regex, max_chars_to_output,
string_description);
You could probably "steal" most of the code for this from Test::More's like
function and add in the functionality for outputting less than or equal to
max_chars
I'll admit I sometimes can't think that far ahead to see all of the
problems, but when I have problems sitting in front of me, I can
usually solve them.
The situation we have now is: Parrot is a VM, and technically we could
just punt the whole calling convention issue to a high level languages foru
At 01:45 AM 11/17/2003 +, Jonathan Worthington wrote:
> I've attached a couple of working samples.
Please may I suggest/request that you pop them in the imcc/examples
directory? There's very little in there as it stands; it'd be nice to at
least put examples in that demonstrate things that are
I've run into a couple of issue with library loading which have their
origin down inside the IMCC code:
1) External libraries are being loaded at parse time.
Inside of INS() in imcc/parser_util.c, Parrot_load_lib() is called at
parse-time when loadlib is encountered. This is causing libraries t
> Various people have bugged me about this for a long time so I figured
> it was time, since it was the logical next step in hiding the Parrot
> calling convention implementation details.
>
> I've patched in initial support for IMCC to compile high level sub calls.
>
> 0, 1 and multiple return valu
At 07:51 PM 11/16/2003 -0500, Dan Sugalski wrote:
At 4:00 PM -0800 11/16/03, Joe Wilson wrote:
Dan Sugalski wrote:
1) The changes I proposed are going in. We get arg counts for I/S/N
registers if they're used.
What purpose do these individual I/S/N arg counts serve exactly?
You missed a bit when
Various people have bugged me about this for a long time so I figured
it was time, since it was the logical next step in hiding the Parrot
calling convention implementation details.
I've patched in initial support for IMCC to compile high level sub calls.
0, 1 and multiple return values are suppor
At 4:00 PM -0800 11/16/03, Joe Wilson wrote:
Dan Sugalski wrote:
1) The changes I proposed are going in. We get arg counts for I/S/N
registers if they're used.
What purpose do these individual I/S/N arg counts serve exactly?
You missed a bit when quoting. This bit, specifically:
Everyone can cop
Dan Sugalski wrote:
> 1) The changes I proposed are going in. We get arg counts for I/S/N
> registers if they're used.
What purpose do these individual I/S/N arg counts serve exactly?
To simply check how many arguments are passed to a function you would
need to get the sum of the number of I/S/N
Okay, I've lost any free time I might have and the discussion's
gotten to the point where it's obvious that we're not going to get
anywhere. So, this is what we're going to do:
1) The changes I proposed are going in. We get arg counts for I/S/N
registers if they're used. Everyone can cope. (You
At 11:57 AM -0500 11/14/03, Gordon Henriksen wrote:
Melvin Smith <[EMAIL PROTECTED]> wrote:
The easy situation is when argument counts change, but the
hard situation is
when semantics have changed. In that case we have to have some
sort of version requirement in the bytecode.
Best practice I'v
Mark Stosberg wrote in perl.qa :
> I'm frequently using 'like' to test $agent->content against a regular
> expression.
>
> When I have a lot of these in a new test script and they are all
> failing, I get a boatload of HTML source floating by, which
> makes it tedious at times to find out what a
13 matches
Mail list logo
