commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32360] - [jxpath] Default Namespace not handled correctly
Date Mon, 31 Oct 2005 18:23:07 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32360>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32360





------- Additional Comments From agallardo@agsoftware.dnsalias.com  2005-10-31 19:23 -------
(In reply to comment #21)
> To the extent there is a real issue here (and I'm not yet convinced there is
> one) it is a disagreement with a deliberate design decision in XPath 1.0. JXPath
> is the wrong place to address this. One would expect a Java compiler to
> correctly implement the Java specification and not provide switches to behave in
> a nonconfiormant fashion. One similarly expects an XPath library to correctly
> implement the XPath specification. 

Well, this is exactly the case every java compiler do. In the following link
read about "non standard options":

http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javac.html#options

I agree this does not show a different behavior of the compiler. But make a
point about non-standard options beyond the specification added because people
found that useful.

For a sample about changing the compiler behavior, lets take java 5 compiler.

In java 5 was introduced the new keyword "enum" wich has been used for long time
as a variable name in a lot of code (BTW, you can find "enum" as a variable name
inside the code of commons-jxpath too).

Based in the java 5 specs, since "enum" is a keyword, there is no way to it as a
variable name. But there is a workaround to change the compiler behavior:

Turn on the compiler flag "-source 1.4" and all the new java 5 lenguage features
are gone! 

(See at the end of http://java.sun.com/j2se/1.5.0/compatibility.html ).

Changed the compiler behavior outside the specs? Yes. Why? To make the software
more usable! ;-)


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message