Nitzan,
Today I've added PKG_ADD & PKG_DEL to the io package, inspired by your
first versions.
I chose to simplify them (as outlined in earlier e-mails:
1. chk_spreadsheet_support.m was especially written to deal with
almost all hassle you've put in PKG_ADD. I'm very sorry for all your
efforts put in PKG_ADD because this wasn't clear;
2. I'd rather use generic names for the Java class libs, sufficiently
unique to be sure they're the right ones, but not including the version
in the names.
3. I dropped all messages. I don't like package-specific verbosity,
and AFAIK no other OF-packages yield start-up messages. Users can always
invoke chk_spreadsheet_support to find out more.
Furthermore, PKG_ADD now expects the class libs in /<libdir>/java/ where
libdir is given by octave_config_info ("libdir").
On MinGW that usually is /lib, so jars are expected to be in /lib/java.
If they aren't found there, too bad, the user can add them by hand (or
in octaverc) using javaaddpath or chk_spreadsheet_support.
PKG_DEL is just a placeholder.
I can see no harm in having classlibs in the javaclasspath for the
remainder of the Octave session after unloading the io pkg; and the
javaaddpath call (which is also invoked by chk_spreadsheet_support)
avoids duplicate entries in the javaclasspath anyway so a subsequent
package reload won't do harm.
Thanks +best wishes,
Philip
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev
