So does that mean, the only set ops will be those that take two registers of the same type?
set_p_p set_i_i set_s_s set_n_n -- Jonathan Sillito (who is willing to help with the migration) > -----Original Message----- > From: Peter Gibbs [mailto:[EMAIL PROTECTED]] > Sent: October 3, 2002 11:43 PM > To: Leopold Toetsch; [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: [perl #17739] [PATCH] Tests for assign ops > > > Leopold Toetsch wrote: > > Nothing against the tests - it's always a good thing to have > tests - but > > I'm confused: > > > > inline op set(inout PMC, in INT) { > > $1->vtable->set_integer_native(interpreter, $1, $2); > > goto NEXT(); > > } > > inline op assign(inout PMC, in INT) { > > $1->vtable->set_integer_native(interpreter, $1, $2); > > goto NEXT(); > > } > > > > and so on. > > > > So what is the _difference_ between set and assign? > > The 'assign' opcodes were intended to replace 'set' for the > situations where the value of a PMC was being updated, > rather than the PMC register being changed. > There are a lot of changes needed to existing code (e.g. > most of the tests) before the 'set' versions can be deleted. > -- > Peter Gibbs > EmKel Systems > >
