🚀 go-pugleaf

Hans Galema wrote:

> > 4.2.1. Definition:Object name
> > A sequence of any characters except �\� and �:�.
> 
> So '/' is allowed.

No that's considered to be a post-processing feature. Again it's about
standardising. Paths while we are working on/with them have '\'. If
they need to have '/' the conversion is performed as late as possible
and is considered to be a 'fix up' operation.

> C:\ape\
> is not a directory path ?

Heh, generally we would say that it is but officially it's a volume ID
and directory path. At the moment the distinction doesn't really matter
but if we ever move development to Linux it might become more important.

> Sorry, but you should first define what a fully qualified path is,
> before you show how it looks, I think.

You could be right. Changes to our database recently and even corporate
structure mean that we are going to have to revisit our path handling
anyway. We have extensions that allow us to specify virtual files
(files within databases so a path containing two paths <g>) and a
subset for specificying devices (like the Windows \\.\ syntax) and they
haven't changed in over a decade.

> And is this covered:
> \\computername\c\apes\
> 
> Just some thoughts FWIW.

It's not, no. All our I/O is performed using the wide path form so the
'\\' would be stripped off prior to processing then added later. That
would produce a relative path so some functionality might get confused.
Normal I/O seems fine having tested it but I think some of our database
handling might a bit upset not having a volume ID.
-- 
Andrue Cope [TeamB]
[Bicester, Uk]
http://info.borland.com/newsgroups/guide.html