I think originally I used IDs for strings to avoid string copying. This was a
bit misguided, as string copying isn't really a big part of WaitZar's
performance anyway.
Also, adding in things like symbols and pat-sint words (which have different
_displays_ depending on where they're shown) really complicated the whole
thing, leading (possibly) to a bug in Burglish.
We should really abstract a "candidate" into a class, to avoid all this array
nonsense. Then, it'd be much easier to add/sub candidates. We should also use
this class wherever possible, instead of relying on IDs (which cause similar
errors to pointers if not managed correctly.)
Original issue reported on code.google.com by seth.h...@gmail.com on 12 Dec 2010 at 6:28
Original issue reported on code.google.com by
seth.h...@gmail.com
on 12 Dec 2010 at 6:28