Repository navigation
Complicated translation result #257
Description
Hi! I tried to translate the following snippet:
def myC():
class c:
value = 11
def getValue(self): return self.value
class d(c): pass
o = d()
return o.getValue() == 11Expected something similar to this, but got
memory > xd
memory > xc
[] > sample
[args...] > unsupported
[args...] > xunsupported
memory > bogusForceDataize
memory > xbogusForceDataize
memory > xhack
seq > @
xhack.write
[]
memory > xmyC
seq > @
xmyC.write
[]
memory > xgetValue
memory > xvalue
memory > xo
seq > @
seq
(((unsupported)) 0)
seq
xvalue.write 11
xgetValue.write
[xself]
seq > @
(((unsupported)) (((xself).xvalue)))
(((unsupported)) ((xc)))
xo.write (((xd)) 0)
(((unsupported)) ((((((xo).xgetValue)) 0).eq 11)))
Activity
dours commentedon May 31, 2022
@br4ch1st0chr0n3 Hello. Thank you for describing your expectations. What steps do you follow to generate EO? You should have recieved this output (it is even more complicated than what you got above): simplest-derived-class.txt
The following text applies to the output that you should have actually received as mentioned above.
TLDR: My generator must be able to support different general python features, which do not happen in this particular example. I try to explain them below. I could elaborate more on the explanation. Please tell me, which of the generalizations hurt you most, so that I reflected on how to simplify them.
Some explanations:
valueis mutable, so we cannot generate11 > value, we must generatecage > valueand then assign 11 tovaluesomewhere else during dataization. "Somewhere else" is calledinitFieldsin my code. It is called before calling a constructorgetValueis also mutable! One can define a functiongetValueand then assign an integer togetValue. This is allowed in python, sogetValuemust also be acage, which stores an object with the function. Currently it is implemented with an anonymous object with a single field calledapply. More fields should be added later because each function in python has fields (!), for example, the__class__fieldreturn. This means that I must support quitting a function at any place inside the function's code. This is implemented with the help of thegotoobject in EO, which has a kind of "calling convention". So, each function, includinggetValuemust be wrapped in an object to be called with thegotoreturn, python has exceptions and break/continue. They are supported through the same mechanism as thereturn, which forces me to analyze each returned value to check if it is actually a returned value or an exception or a break/return. This part is described here Memo: implementation of break and exceptions in python with goto in EO objectionary/eo#618 . This is whygetValue()is called likegoto, so a class is also called the same way:(goto ((((xd)).apply).@))creates an object of the classd..<fielddeemp commentedon Jun 2, 2022
Hi! Thank you for your comprehensive feedback. We need some time to discuss it with the odin team.
Regarding the output, I got it by following the instructions from README. However, it refers to an old version of the transpiler. Please, update the link (also suggested here).