#362: GET-JAVA-FIELD doesn't behave orthogonally when TRY-HARDER is T -----------------------------+----------------------- Reporter: robert goldman | Owner: mevenson Type: defect | Status: closed Priority: major | Milestone: 1.4.0 Component: JSS | Version: 1.4.0-dev Resolution: fixed | Keywords: -----------------------------+-----------------------
Comment (by robert goldman):
Here's a patch for this. I also added a condition for not finding the field. I'm not sure that's the right thing, though, so perhaps a simple `ERROR` as in the current code would be better. Here's why: if we fail to find the field in the JSS code, when `try-harder` is non-`NIL` you get a special condition. But if `try-harder` is `nil`, you fall through to the JFFI code, where you ''don't'' get this condition.
In general, this is probably an artifact of the split between JSS and JFFI, which seems undesirable. It would be nice to simply fuse JSS into JFFI so that there's only one JFFI to keep track of....
-- Ticket URL: http://abcl.org/trac/ticket/362#comment:5 armedbear http://abcl.org armedbear