|
From: Stefan S. <s...@xs...> - 2009-04-24 09:27:59
|
On Fri, 24 Apr 2009 01:21:28 -0500 Slava Pestov <sl...@fa...> wrote: > On Fri, Apr 24, 2009 at 12:59 AM, Stefan Schmiedl <s...@xs...> wrote: > > > > git pull > > rm boot.unix-x86.64.image > > make clean > > make > > wget http://factorcode.org/images/latest/boot.unix-x86.64.image > > ./factor -i=boot.unix-x86.64.image > > chmod a-w factor.image > > ./factor -i=factor.image -e='USING: system memory ; IN: > > scratchpad : bye ( -- ) 0 exit ; "virgin.image" save-image-and-exit' > > > > At this point I can ./factor -i=virgin.image and rely on > > my forth-based muscle memory to exit via bye :-) > > > > Suggestions for improving this? > > If you want to have some libraries always available, or define some > useful utility words, you can put them in your ~/.factor-boot-rc file. > This file is run when bootstrap happens. that is individual bootstrap of the image upon application start as opposed to bootstrapping the factor.image? How does factor handle redefinitions? Is the old implementation of a word still available after redefining it? How does saving an image and reading a startup file work together in factor, anyways? > Also the first part of your script can be replaced by > './build-support/factor.sh update'. ah ... I hadn't looked into that folder yet :-) Thanks, s. |