On Sun, 7 Oct 2001, Dan Sugalski wrote:
> I ended up pitching WinCVS and went with the command-line version. Works
> well enough, though not all that spiffy.
Just a tip:
One of my coworkers had this problem recently and, when he finally gave up
on WinCVS, he was unable to make the command li
[EMAIL PROTECTED] (B Vlad) writes:
> ps. have to figure how to get the WinCVS thing work...
> can't seem to be able to access cvs.perl.org. I've used
> the following set up:
>
> CVSROOT = :pserver:[EMAIL PROTECTED]:/home/perlcvs
> Authentication = passwd file on the remote host.
>
> any suggest
At 03:21 PM 10/6/2001 +0100, Simon Cozens wrote:
>On Sat, Oct 06, 2001 at 09:01:34AM -0500, Gibbs Tanton - tgibbs wrote:
> > which doesn't look that bad. Really, I would imagine all of this would be
> > autogenerated by process_opfunc.pl so it doesn't matter what the longhand
> > looks like.
>
>N
At 01:27 PM 10/6/2001 -0400, Bryan C. Warnock wrote:
>On Saturday 06 October 2001 01:13 pm, Michael Maraist wrote:
> > So would it be something like(ultimtaely put into a macro):
> > AUTO_OP add_p_p_p {
> > if (!P1)
> > CREATE_PMC(P1);
> > if (!P2 || !P3)
> > throw exception; // howeve
At 01:32 PM 10/6/2001 -0700, [EMAIL PROTECTED] wrote:
>ps. have to figure how to get the WinCVS thing work...
>can't seem to be able to access cvs.perl.org. I've used
>the following set up:
>
>CVSROOT = :pserver:[EMAIL PROTECTED]:/home/perlcvs
>Authentication = passwd file on the remote host.
>
>a
EMAIL PROTECTED]:/home/perlcvs
Authentication = passwd file on the remote host.
any suggestion on how to make it work?
-Original Message-
From: Gibbs Tanton - tgibbs [mailto:[EMAIL PROTECTED]]
Sent: Saturday, October 06, 2001 6:12 AM
To: 'Simon Cozens '; '[EMAIL PROTECTED]
On Saturday 06 October 2001 01:13 pm, Michael Maraist wrote:
> So would it be something like(ultimtaely put into a macro):
> AUTO_OP add_p_p_p {
> if (!P1)
> CREATE_PMC(P1);
> if (!P2 || !P3)
> throw exception; // however this is done in Parrot
> P2->vtable->add[P3->type]->(interp, P
On Sat, 6 Oct 2001, Michael Maraist wrote:
> My question at this point is if the PMC's are polymorphic like Perl5
> or if there is an explicit type type. Polymorphics can make for vary
> large vtable sub-arrays. (int, int_float, int_float_string,
> int_string, etc).
>
> If PMC-types are bit-mask
On Sat, 6 Oct 2001, Simon Cozens wrote:
> On Sat, Oct 06, 2001 at 09:01:34AM -0500, Gibbs Tanton - tgibbs wrote:
> > Also, how will adds of different types be handled. In the above if pmc2 is
> > an int and pmc3 is a float we're going to have to know that and do a switch
> > or something to conv
On Sat, Oct 06, 2001 at 09:01:34AM -0500, Gibbs Tanton - tgibbs wrote:
> which doesn't look that bad. Really, I would imagine all of this would be
> autogenerated by process_opfunc.pl so it doesn't matter what the longhand
> looks like.
Not really; I expect that "external" code will also manipul
>> 2.) Can you give an idea of what you think the macro-ized function
should
>> look like (an example would be great.)
>No, because then you'll go away and implement it, and I want to
>encourage
>some fresh blood to do that. :)
Okey Dokey...I promise not to do it :)
>Seriously, before I do tha
On Sat, Oct 06, 2001 at 08:11:30AM -0500, Gibbs Tanton - tgibbs wrote:
> void add( PMC* self, PMC* left, PMC* right );
> does this represent:
> self = left + right
Yes.
--
UNIX was not designed to stop you from doing stupid things, because that
would also stop you from doing clever things.
2 other things
1.) Will each different "type" of PMC have its own vtable, function
definitions, etc or will they all share everything with switches on type in
the function definitions.
2.) Can you give an idea of what you think the macro-ized function should
look like (an example would be great.
for add we will end up with
void add( PMC* self, PMC* left, PMC* right );
does this represent:
self = left + right
or some other ordering?
-Original Message-
From: Simon Cozens
To: [EMAIL PROTECTED]
Sent: 10/6/2001 7:50 AM
Subject: vtable.h
I've just committed some files which genera
14 matches
Mail list logo
