Re: [lizard] Re: A few ideas

[Ravi R. <ram...@gm...>]

On 9/10/05, Ravi Ramaseshan <ram...@gm...> wrote:
> Hi,
>=20
> On 9/10/05, Kalpak Shah <kal...@gm...> wrote:
> > hi aditya,
> >
> >  I tried to follow up on the leads you gave us.
> >
> > On 8/30/05, Aditya Thakur <woo...@ya...> wrote:
> > >
> > > Actually, I can imagine how an inerpreter-like tool could be used to
> > implement reversibility...actually, it would be more of a "reverse
> > interpreter" , very very similar to the reverse instruction generator R=
avi
> > spoke about. So instead of generating (like a compiler) the reverse
> > instructions, you would just do it at runtime (like an interpreter). wh=
at
> > say?
> >
> >  I didnt find any great C interpreters(other than EiC) which could be u=
sed
> > to perform the "reverse interpreter" operation. Also we couldnt come up=
 with
> > any convincing solution for the problem Ravi mentioned. Would this be m=
ore
> > beneficial in presence of available reversible debuggers?
>=20
> Could you please tell us how do you plan on using a C-interpreter ?
> What do you want the interpreter to do exactly ? This C-interpreter
> thing you speak of seems very vague to me.

As far as I see it, the C-interpreter thing is just seems to be a
place where you're going to actually code/instrument-in your reverse
code fragment.

This whole discussion is way too vague ! You couldn't find
C-interpreters to do what exactly ?  What do you mean by "reverse
interpretation" ? What is it supposed to interpret ? At what level are
you working ? Why do you need a  C interpreter ? What is your
objective ?

--=20
Ravi Ramaseshan
http://www.geocities.com/ramaseshan_ravi/

" Reality is only something we believe in strongly. "