[Oberon] Re (2): Recent additions in OLR.

[eas lab]

That seems good, except for M$ users with those absurd
<natural language sentence> FileNames.

Does OLR run on RPi?

When my X86 motherBoard died I panicked and hadn't backups
of the current Aos-files, which ALO could have handled with
difficulty.

== Chris Glur.


On 5/18/16, Peter Matthias <PeterMatthias at web.de> wrote:
>
>
> Am 18.05.2016 um 16:54 schrieb eas lab:
>> With ALO & LNO, which can't access outside of their own directories,
>> I must roam the file-tree eg. with mc, and <3-key-action> write a sLink
>> to the ALO/LNO directory.  Can OLR System.Directory & read/write
>> outside of its own directory?
>
> OLR can use any directory. Limitations are:
> - it must be absolut to root "/" or relative to current directorx "."
> - it must be less than 256 characters long in total
> - whole path must consist of characters allowed for filename as in
> Native Oberon
>
> Last two limitations can easily be extended.
>
> Regards,
> 	Peter
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>