For an example, have a look at the package Helvetia-Loader in http://source.lukas-renggli.ch/helvetia. It verifies the expected sytem, patches Monticello, bootstraps the quasiquoting, replaces the compiler and parser infrastructure in multiple steps, ...
Lukas On Monday, 7 November 2011, Stéphane Ducasse <[email protected]> wrote: > if you look in the scripttloatder you can tell the MC that it should apply a list of package one after the other and not (by default collect all the classes and apply all the change together). > > Now another smart move is to think (if the license allows it) how you can push the hooks that you need to the community like that you are more customization and less override. > Now part two, I hope that we will get a bootstrap working one of these days but for that we need to get time. > > Stef > > On Nov 7, 2011, at 11:29 PM, Stefan Marr wrote: > >> Hi: >> >> I was wondering what the standard approach is to package rather invasive changes to core classes. >> >> >> Currently, I have everything in extension methods that override the existing methods in my own package. >> However, the monticello package is not actually loadable. So, I cannot just load my stuff into a new image via monticello. For instance, I modify #basicNew/#basicNew:, the Parser, the Encoder classes, etc. >> >> With my changes, these things depend on my own classes being properly initialized in the image. >> >> What is the best way to get that into a loadable/bootstrapable state? >> >> Do I need to split up all the stuff into different packages according to dependencies and then make sure that I can load those different packages in a well defined order? >> >> Or is there anything to tell Monticello to be smarter about loading the stuff? >> >> Thanks >> Stefan >> >> -- >> Stefan Marr >> Software Languages Lab >> Vrije Universiteit Brussel >> Pleinlaan 2 / B-1050 Brussels / Belgium >> http://soft.vub.ac.be/~smarr >> Phone: +32 2 629 2974 >> Fax: +32 2 629 3525 >> >> >> > > > -- Lukas Renggli www.lukas-renggli.ch
