|
Authored by: Anonymous on Thursday, May 03 2012 @ 08:07 PM EDT |
"Java makes this sort of dependency searching relatively easy, you can
check the
'import' statements to see where it gets its resources from."
Not quite, because you need to differentiate those parts that are required by
spec, e.g. method signatures or return values and those imports that are just
implementation details.
"An interesting 'find' is the class XMLUtils.... which is a 'private' class
in
java.util used to support the java.util.Properties class....."
Since this is a private class it is an implementation detail and not a
requirement. It isnt even a part of the API since user classes cant see it.[ Reply to This | Parent | # ]
|
- Automation? - Authored by: Ian Al on Friday, May 04 2012 @ 05:51 AM EDT
- Automation? - Authored by: Anonymous on Friday, May 04 2012 @ 08:22 AM EDT
- Automation? - Authored by: Anonymous on Friday, May 04 2012 @ 10:04 AM EDT
|
|
|
|