Print

Print


Actually, I already got past this problem -- there was indeed an issue
(apparently), just not the one the error message seemed to be
complaining about. Anyway, I'm just starting out, with a fast-changing
and error-filled codebase, so you probably don't want to use my code
for debugging anything :)

On Sun, Aug 24, 2008 at 9:31 PM, Sean Luke <[log in to unmask]> wrote:
> On Aug 24, 2008, at 9:15 PM, Andrew Wagner wrote:
>
>> Umm, I hate to be the bearer of bad news, but I'm running on ECJ 18.
>
> Drat!  Okay, I know I fixed it this summer in response to a similar bug
> report.  But it's not listed in the CHANGES, even for the current CVS.  I'm
> declaring it an ECJ19/CVS change.  ;-)  Tell me if the following file gives
> you a different, more logical response.
>
>
>
>
>
> Sean
>
>
>