home *** CD-ROM | disk | FTP | other *** search
- GNU Smalltalk 1.1.1
- -------------------
-
- This is the first (public) release of the GNU Smalltalk interpreter for the
- Archimedes.
- As such I would be grateful to hear of any problems relating to its use and
- likewise and problems encountered with running code that should work.
-
-
- Running GNU Smalltalk
- ---------------------
- Because it is not a small language and has rather hefty memory requirements,
- this is not really useable on a 2Meg machine - however you might just get it
- to work if you do the following
-
- o exit the desktop
- o run 'mst'
-
- If you get errors of the form :
-
- Internal abort on data transfer at 00008078
-
- You haven't got enough memory. Sorry about this - it does rather hefty malloc
- calls for not inconsequential amounts of memory.
- (As standard for the atari ST it would try malloc'ing 4Meg in one go. Yuk -
- I've changed it so it only asks for two.
- If you have a machine with piles of memory then read on ;-)
- )
-
- If you have a really small amount of memory in your machine then the best way
- to see if Smalltalk will run is to exit the desktop and try the 'st' alias
- that is setup to run it - this should either work or give an internal abort;
- in which case you will know definitely whether it will or won't work.
-
-
- Bootstrapping Smalltalk
- -----------------------
- By default, smalltalk looks for an image file which is made up from those
- smalltalk files used to boot the system; these are present in !GNUst.st .
- It is entirely possible to rebootstrap the system as follows :
-
- o copy !GNUst.image (the original kernel image) somewhere safe
- o edit !GNUst.st.whatever
- o re-run smalltalk
-
- This should now gives messages about 'Processing...' and then a new kernel
- image file.
- This should be copied into !GNUst.image and then the new image will be loaded
- upon every startup.
- However! If you have a file present in the current directory called
- mst/im
- that will be loaded in preference to the default kernel image; so it is
- important to move your new kernel into !GNUst once you have made any changes
- so that it is loaded - the file mst/im is created in the current directory
- after bootstrapping; so the process should be (continued from above) :
-
- o find the new mst/im file
- o copy this to !GNUst.image
- o delete mst/im file
- o ready to try new kernel image
-
- Note that any changes to any of the kernel smalltalk files will result in
- GNU Smalltalk trying to rebuild a new image - if you wish to prevent this
- having edited something then changed it back; then restamp the image file -
- this will ensure it is newer or as new as any of the sources.
- If you are saving your own images then using -I will work with the command
- line alias - if you then copy it to !GNUst.image it will load any of your
- objects / methods as well.
- (see the tutorial)
-
-
- People with indecently large amounts of memory
- ----------------------------------------------
- There is a second binary (mst_large) which uses twice as much memory as the
- usual version - try this if you have got around 4meg to spare...
-
-
- Bugs
- ----
- Gives abort on data transfer messages when out of memory or can't malloc
- enough.
- Also :
- 'Out of malloc/swap space'
- type messages are indicative of the same problem.
-
-
-
- hope someone finds it useful...
- al slater.
- 24/6/94
-
- bug reports / problems can be sent to :
-
- ams@csd.abdn.ac.uk
-
- or via snailmail:
- kintail,
- barclay park,
- aboyne,
- aberdeenshire.
- ab34 5jf.