couple of things concerning mathpiper2
Sherm Ostrowsky
1. when doing ant *all on mathpiper2, I get a lot of javac "errors" about classpath for bootstrap not present. Is this important?
2. when compiling (shift_enter) a .mpw file in mathpiper2, if there is an error on line xxx, the error message ALWAYS quotes the next (active) line as the place of error, e.g., xxx+1 (if that line is not a comment).
Sherm
Ted Kosan
> 1. when doing ant *all on mathpiper2, I get a lot of javac "errors" about
> classpath for bootstrap not present. Is this important?
I don't see these errors when I do an ant *all. If you send me a copy
(off list) of the output that is generated when you do an ant *all, I
will look at it and try to figure out what is wrong.
> 2. when compiling (shift_enter) a .mpw file in mathpiper2, if there is an
> error on line xxx, the error message ALWAYS quotes the next (active) line as
> the place of error, e.g., xxx+1 (if that line is not a comment).
I started heavily modifying the error reporting system early in
September and I have not finished with this work yet. I have found
that my students tend to generate errors in numerous surprising ways
and I have been collecting examples of the code that produces these
errors when I can. Over time, as I enhance the error reporting system
to handle these various error types, the accuracy of the line numbers
that are reported should improve.
On a related note, sometimes a student is able to crash MathPiper and
I am unable to determine how it was done because I do not have a
record of the steps they performed to produce the crash. I am thinking
that eventually I would like to create the ability for MathPiper to
record every evaluation a user requests it to perform so that I can
recreate these crashes and fix the bugs that are allowing them to
happen.
Ted