home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.acorn.tech
- Path: sparky!uunet!inmos!fulcrum!bham!warwick!pavo.csi.cam.ac.uk!cl.cam.ac.uk!crj10
- From: crj10@phx.cam.ac.uk (Clive Jones)
- Subject: Re: RISCOS_lib and alternatives
- Message-ID: <1993Jan28.180338.12327@infodev.cam.ac.uk>
- Telephone-Messages: +44 223 33 4900
- Sender: news@infodev.cam.ac.uk (USENET news)
- Address: Christ's College, Cambridge CB2 3BU, ENGLAND.
- Nntp-Posting-Host: easton.cl.cam.ac.uk
- Organization: Cambridge University Computer Laboratory
- References: <1k624eINN74o@motmot.doc.ic.ac.uk> <1993Jan27.142801.9279@csc.ti.com>
- Date: Thu, 28 Jan 1993 18:03:38 GMT
- Lines: 17
-
- In article <1993Jan27.142801.9279@csc.ti.com> a909937@tiuk.ti.com writes:
- >RiscOSLib is included in the sharedClibrary in the ROM's of
- >RiscOS 3.10. What is required is for Acorn to release the object
- >file to link with, so come on Acorn where is it.
-
- There isn't one, and one can't be written. Acorn has explained this in
- c.s.a.tech some time ago. The problem is that the RiscOSLib in
- question is somewhat neutered - it has lots of unwanted routines
- pruned out if not needed by the ROM, so that things fit. Also, a lot
- of stack checking and such has been removed. To make matters worse,
- the code is tacked on to the end of SharedCLibrary, and the
- applications in ROM are linked directly to it. This means that the
- entry points cannot be guaranteed to stay in the same place in future
- releases of the ROM. Thus, you'd throw portability out of the window
- if you linked to it from code that is not part of the ROM.
-
- --Clive.
-