|
> From: Jon Paris > > In other words - the problem would > appear to lie with Windows, not with IBM. If even MS cannot get > installs to work on their own OS what hope for anyone else? I don't want to get too involved in this debate - got three demos this week, and the Eclipse book just went to press, so I'm beat - but one truism about Windows is that if you use the registry, you are asking for trouble. Eclipse, which doesn't use anything in the registry and simply uses configuration files in its own little directory, almost never botches up, and I can have multiple copies with no problem. In fact, I currently have four different versions of Eclipse installed on my workstation (in order to keep track of screen captures for my book during the many changes leading up to the final release of version 2.1). On the other hand, if I understand correctly you can only have one version of WDSCi at any one time, and you have to be careful about installing one over the other. Now, since WDSCi is in theory Eclipse++, it seems that the WDSCi portion of the code broke the stability of Eclipse. So do we laud IBM for creating a truly stellar product in Eclipse, or vilify them for trashing it with WDSC? I suppose it depends on your mood <grin>. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.