Profile for jools

Contact	About me
Email: Private ICQ: AOL: Yahoo:	Username: jools Realname: Steven Simpson About me: Homepage: http://www.comp.lancs.ac.uk/~ss/ Face/Logo: Comments posted: 6 (show all)

Recent comments

On ROL release C99 SCL to A9home users:

wuerthne: You're right, of course, if they're free to choose what feature to add next. But since it's the C library, at least they could standardize on coarse version numbers for coarse features e.g. C89, C95, C99. !Run files can look for just those, leaving the !System installer to deal with the finer details. jools on 18/4/06 4:32PM [ Reply | Permalink | Report ]

On ROL release C99 SCL to A9home users:

Will developers have to alter their applications' !Run files to correctly load a C99-capable SCL, or are they fine as they stand? If StubsG isn't used? What does it mean to (not) 'play the version numbers game'? Certainly, Castle and A6 shouldn't have competing version-number schemes - that renders them useless. Even if they had different implementations, they could still agree on which versions introduce which functionality, couldn't they? jools on 18/4/06 12:34PM [ Reply | Permalink | Report ]

On RISC OS Shared Libraries:

Anyone still reading this? Well, I think I've done it. jools on 09/12/03 00:00AM [ Reply | Permalink | Report ]

On RISC OS Shared Libraries:

A-ha, I see a call to main() in unixlib/source/unix/unix.c in the old gccsdk I've been using. Is that the right place? Will drlink -aof incorporate any static libraries, so I can easily determine all the provided and required symbols in a single format I'm already familiar with? I guess I'll try it anyway... Cheers again. jools on 05/10/03 8:16PM [ Reply | Permalink | Report ]

On RISC OS Shared Libraries:

So, can anyone suggest how I should go about linking shared libraries to actual executables? (This is the reason why I haven't really progressed since the original announcement.) One idea is to get a static linker to insert code and data to be executed before main() to cause the libraries to be loaded, analogous to (or augmenting) the SharedCLib stubs. How difficult would this be? It would need to insert a symbol table and relocation directives into the executable, so that the libraries and the main application could refer to each other by name. Another is to have some sort of AOF loader (okay, maybe an ELF one later, but I've got AOF ready now). It would probably have to be a module, one that was OS_Module-2 entered. Would it be able to make use of the C env provided by SharedCLib without clashing with its own intentions for application space? Any more concrete ideas? Cheers! jools on 05/10/03 6:32PM [ Reply | Permalink | Report ]

Search the archives

Today's featured article

The new apple of my eye
Would you swap your dusty Acorn for a polished Apple computer? Martin Hansen has been checking out the world of Steve Jobs and his range of shiny kit.
 15 comments, latest by adh1003 on 6/1/09 1:06PM. Published: 17 Nov 2008

Random article

RISC OS Memory Protection
Corruption at the lowest levels
 25 comments, latest by Jaco on 30/4/05 9:54AM. Published: 25 Apr 2005

Useful links