Hi,
I don't want to be the party's troublemaker, but I
wanted to point out the danger of (as we say in french),
"to throw the baby with the (dirty) water of the bath ".
(rough translation of "Jeter le bebe avec l'eau du
bain" ICYWI).
That is, if I agree with Ernest proposition to make
things cleaner , I don't believe the new version should
forget the legacy java programs. First, it will give
a "never final" product and scares out further "java"
development. (this is for the marketting (sic) point of
view).
I trust in a "compromise view". I propose to keep an
entry-point called jess.java which would be only an
interface to the newly designed "Shell" or "SJess" file.
This interface would only call SJess functions.(Maybe
inheritance could solve that).
Therefore, choice of entry point would remain in the
hand of the developper.
Unless the implementation is not that obvious, I expect
this solution to satisfy everyone AND without coming to
awfull compatibility solution.
Of course, I may have overlooked something, but reforms
should always be cautious :-)
Cordially
Erwan
PS: I admit I would personnaly use the newly designed
classes !
====================================
Erwan TRANVOUEZ
_______
E-mail: [EMAIL PROTECTED]
URL: http://www.chez.com/etranvouez
____________________________________
Telephone Personnel/Personal Phone Number
+33/6 09 58 36 96
______________________________________
Votre e-mail, votre site perso en quelques clics ...
c'est simple et gratuit sur Chez.com
http://www.chez.com --------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] ---------------------------------------------------------------------
