ML>>  JD> porting of stuff like BRE, etc.  Some of the code relies heavily
 ML>> can you give some examples of bugs that are relied on?

 JD> Honestly, I don't want to be too specific here (for fear of
 JD> further cheat exploits on the system).  I will give the
 JD> example though of porting the registration code generation
 JD> routines for the SR products to another language -- where I
 JD> had to add a bunch of extra code to simulate the way that BP
 JD> handles Integer values.

oh yes... in that particular situation, though, i'd do a completely new
registration method and just move on leaving the old, bad, nasty stuff
behind... give those with valid codes and credentials new codes or require
a small upgrade fee for the registration stuffs or something similar...
either way, i'd rather move on rather than to stay mired...

 JD> This example is really a combination of poor compiler
 JD> behavior and bad programming practices, but regardless, it
 JD> keeps the code from porting well.

true...

)\/(ark