🚀 go-pugleaf

In article 12969@cs.aukuni.ac.nz, jwil1@cs.aukuni.ac.nz (TMOTA) writes:
>burke@vxdesy.desy.de writes:
>
>
>This is why I advocate SOURCE libraries, and focus the attention of my
>library upon the small, useful, stand-alone functions that are handy, rather
>than an all-singing, all-dancing organism.
>
>With a choice of several event handlers, you can choose the one that is
>closest to what you want, and then alter the source to do *exactly* what
>you want.
>-- 
>_________________  "I'd like to answer this question in two ways:
>  /____ _ _/_ __       First in my normal voice, and then
> // / //_//_ /_/       in a silly, high-pitched whine." (Monty Python)

I have no experience with the ARM-based acorns yet, but I'm about
to...  If RISCOS supports dynamic linking, I would strongly support
using libraries, and not source reuse. It could save you a lot of disk
space, and with a good implementation of shared libs, a memory saving
while running as well.

If you make a bugfix on a shared lib, all apps using it will be fixed
automagically as well.

If RISCOS doesn't support shared libs, source reuse can be ok. At least
if you don't write portable applications. If you want your apps to be
portable to other environments, shared libs may enter the picture
again.

I expect to do most of my programming in RISCiX, as I want my programs
to be easily ported to Sun's. I just have to get this beast running....


---
Birger A. Wathne
Email  : birger@sdata.no        birger@ii.uib.no
Private: Fjoesangervn. 133, N-5032 Minde           Tel: +47 5 200062
Work   : Skrivervik Data A/S                       Tel: +47 5 543740
         Thormoehlensgt 55, N-5008 Bergen          Fax: +47 5 322853