You are in a maze of twisty little passages, all alike.
Posted by pookzilla on January 11, 2008
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. 
JanDiederich said,
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.
pookzilla said,
Jan: it’s more to do with bug 214904 and 215030.
Chris Recoskie said,
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…
pookzilla said,
Chris: I meant what I said.
As for the secret… well, that’s an old family recipe.
Add A Comment