Path: utzoo!attcan!uunet!mcsun!ukc!axion!rtf.bt.co.uk!brian
From: brian@rtf.bt.co.uk (Brian N Butterworth)
Newsgroups: comp.sys.acorn
Subject: Re: Filing system matters
Message-ID: <1991Feb10.135550.13566@rtf.bt.co.uk>
Date: 10 Feb 91 13:55:50 GMT
References: <795@utrcu1.UUCP>
Organization: British Telecom Customer Systems, Brighton, UK
Lines: 28

In article <795@utrcu1.UUCP> kortink@utrcu1.UUCP (Kortink John) writes:
>dhmyrdal@lise.unit.no (Dag Haakon Myrdal) writes :
>
>> (For those having access to a VAX: yes, this is similar to the way 
>> the VAX handles file version-numbers)
>
>Personally, I find VAX's version numbers a pain in the ***.
>
>But unlimited length (well, up to disc space at least :-) filenames a-la
>Unix would be great. Also, maybe a filetype could define an implicit
>filename extension, like &FFF would make a file 'zap' be a 'zap.txt'.
>Unix-like file links would be great too (but I realise this may need
>a double-linked directory structure).

If links were needed, they could in places be made by having a filetype 
which contains the linked to filename in ascii format.

If this file is accessed by OS_File and OS_Find, the alternative file
is read.

Anyone fancy having a go?

-----
Brian N Butterworth (brian@rtf.bt.co.uk) (Netware: bsc486/brian)
British Telecom Customer Systems  |  Telephone: DDI (0273) 762106
Hyperion House                    |             S/B (0273) 206551 x 2106
96-99 Queens Road                 |  Facsimile:     (0273) 722038
Brighton BN1 3XF.                 |             or  (0273) 762071 (Netfax)