While trying to clean up and refactor the Equinox XSLT transform code (a moderately complex Equinox framework extension broken out among several bundles) that I wrote last year I find myself in one of three situations:
- I can have code that doesn’t compile without discouraged access warnings but works just fine in a running instance.
- I can have code that compiles cleanly but wont actually work in a running instance by virtue of how Equinox loads framework extensions.
- I can have code that compiles cleanly, runs fine, but is held together by spite, twine, and reflection.
Sigh.
Some days you’re the windshield, other days you’re the bug. 
4 responses so far ↓
1 JanDiederich // Jan 14, 2008 at 3:36 am
Well, I should make it clear that I had never problems with your XSLT transformation code. But examples are, and should be, generally very arbitrary. And in my case I could really shrink the code a much, with transforming it to my special target.
2 pookzilla // Jan 14, 2008 at 8:57 am
Jan: it’s more to do with bug 214904 and 215030.
3 Chris Recoskie // Jan 14, 2008 at 9:41 am
I think you meant that your code is held together with “spit” and not “spite”
Although, if you really meant spite, I want to know your secret, because I have a lot of spite saved up that could be put to good use…
4 pookzilla // Jan 14, 2008 at 9:48 am
Chris: I meant what I said.
As for the secret… well, that’s an old family recipe.
Leave a Comment