* Will the idea of platform-universal components revived? If yes, the
platform-sensitive components files can be discontinued. I personally
like the idea, though?
The problem is that modern operating systems suffer from a
multi-personality problem. There is not "the" platform that you are
running on, but every framework might have its own platform: ML, JVM,
the settings environment (e.g. native windows vs. cygwin), certain tools.
So our classic universal component idea was already right, because it is
then up to the component settings to work out the details of the platform.
OK, once the universal Java is there, this disjunctive switch can be
discontinued. Fine.
* Cleanup and maintainance of nfsbroy:/home/isabelle/contrib
We now have several component directories, which is the real one?
/home/isabelle/contrib #haftmann
/home/isabelle/contrib_devel #haftmann
/home/isabelle/public_components #krauss
/home/isabelle/website-Isabelle2012/dist/contrib #wenzelm (official
release)
»/home/isabelle/contrib« is supposed to be »the« place finally, which is
very likely to be a superset of
»/home/isabelle/website-IsabelleYYYY/dist/contrib«.
»/home/isabelle/contrib_devel« will stay until mira and isatest are
migrated to use Admin/components.
Not sure what the status of »/home/isabelle/public_components« is.
Florian
--
PGP available:
http://home.informatik.tu-muenchen.de/haftmann/pgp/florian_haftmann_at_informatik_tu_muenchen_de
_______________________________________________
isabelle-dev mailing list
[email protected]
https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
