What specific problem are you having debugging? Stepping Through a block which about to send message to a Proxy? It seems like I should be having the same problem with Magma proxies.. I know sometimes I would get a "Simulation" error while stepping Through (which would blow up a debugging session) but that may have been caused by something else because I don't remember seeing even that in a while..
I may be doing something different in my Proxy-reification process than Glorp which lets it work even without using mirror primitives (unless I'm using them without knowing it -- I'm not sure how they work or even what they are)..? On Mon, Jun 23, 2014 at 3:16 PM, Esteban A. Maringolo <emaring...@gmail.com> wrote: > 2014-06-23 16:59 GMT-03:00 Esteban Lorenzano <esteba...@gmail.com>: >> sad, but understandable. >> in any case, it is a work for the pharo *community*, not for the consortium. >> things that would help: >> - an entry in the issue tracker >> - an explanation of the use case needed to solve >> - a pointer to Eliot modifications in squeak so the one who will do the job >> can take a look > > I added an entry to the issue tracker: > https://pharo.fogbugz.com/f/cases/13377/Mirror-primitives-in-Debugger > > Which also refers back to this post, possibly causing an infinite recursion :) > >>> I hope somebody from Pharo with enough internals knowledge will pick this >>> up. >>> >>> GLORP is the only ORM we have in Pharo 3, and debugging objects being >>> mapped can get really nasty. > >> any other ORM you would do would use also proxies, so you would have the >> same problem :) > > I know, but that doesn't make my statement false. :) > >> is not a problem of GLORP but a problem in our support for proxies. > > What else uses this kind of proxies? > > > Regards! > > Esteban A. Maringolo >
