I'll admit to have limited knowledge of j.l.instrument (and right now not even enough time to read through the API docs), but doesn't that allow hooking into the class definition process only? It still wouldn't allow you to hot-replace code of an already defined class AFAIK (I might be wrong), which I believe is the "Eclipse capability" the poster I replied to talked about.
Attila. On 2008.01.30., at 14:31, Rémi Forax wrote: > > Attila Szegedi a écrit : >> That's an entirely different aspect -- there is the JVMTI (JVM Tools >> Interface) that allows you to do this kind of operations on a JVM >> from >> a native (C-linked) code module loaded into the JVM process itself - >> debugging, profiling, hot code replacement, whatnot. It is generally >> not available as an implementation-independent facility to programs >> running within the JVM itself. There are some "standard" native >> modules that'll then an out-of-process bridge for, say, debugging >> (i.e. a low-level JDI protocol upon which the higher level JPDA is >> built). >> >> But JVMTI/JDI/JPDA can't be considered to be standard facilities >> available to code running within the JVM, so you it's generally a bad >> idea to base your code logic on them :-) >> >> Attila. >> > hum, yo forget java.lang.instrument. > > Rémi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
