8 bit os_f handles

Stewart Brodie stewart.brodie at pace.co.uk
Mon Mar 27 11:05:46 BST 2000


In message <Marcel-1.53-0325135756-3136#xE at druck.freeuk.com>
          "David J. Ruck" <druck at freeuk.com> wrote:

> On Sat 25 Mar, Jonathan Coxhead wrote:
> 
> >    (2) Throughout RISC O S, the code assumes its a byte, so it's not 
> > going to change.

ISTR that somebody wrote an OS extension that intercepted the filing system
vectors and used "large" file handles to record information about file locks
and other stuff.

> On a slighly different note; everyone should be thinking ARM 32 bit mode
> conversion from now on. Its going to be a vast amount of work for every
> RISC OS developer

I disagree.  C programmers will have no difficulty.  Assembler programmers
will have recipes for changing code.

>  and one of the things we need to rely on is that essential libraries such
> as OSLib, will be both 32bit ready and cater for all existing API's and new
> extensions. Removing potential problems such as os_f now, will mean a lot
> less work over the cirtical times to come.

Making defmod capable of generating the correct stuff for 32-bit support is
trivial.

-- 
Stewart Brodie, Senior Software Engineer    (Views expressed are my own and
Pace Micro Technology PLC                   not those of my employer)
645 Newmarket Road
Cambridge, CB5 8PB, United Kingdom         WWW: http://www.pacemicro.com/



More information about the oslib-user mailing list