3 ms·
Gregor Kiczales, the guy behind Aspect Oriented Programming, said something like Common Lisp couldn't attain the level of (aspect oriented) tooling that Java c
by EdwardCoffin 2y ago
Gregor Kiczales, the guy behind Aspect Oriented Programming, said something like Common Lisp couldn't attain the level of (aspect oriented) tooling that Java could, because the tools in Common Lisp could not be sure what the Lisp code they were analyzing actually does, but in Java the language is constrained enough that the tools can figure it out. He said this in a MOP retrospective he gave at the Vancouver Lisp User's Group meeting on 28 June 2006 [1]. There's a link to an .ogg file in the link below, and he talks about this at around the 45 minute mark.
[1] https://web.archive.org/web/20060821003818/http://bc.tech.coop/blog/060709.html https://web.archive.org/web/20060821003818/http://bc.tech.co...
- kazinator 2y ago> but in Java the language is constrained enough that the tools can figure it out So, ironically, the AOP tooling both takes advantage of this issue and fixes it in the same stroke. Once you have an AOP-endowed language like AspectJ, tooling can no longer know what code does