riscosify() and guess_or_null()

Nick Burrett nick at dsvr.net
Tue Sep 30 05:49:23 PDT 2003

John Tytgat wrote:
> Hi,
> I just got a bug report from a CVS user which boiled down to a bit of
> heuristic code in the UnixLib riscosify() routines.  I.e. the code tries
> to figure out if the incoming filespec is a Unix or RISC OS file spec.
> Normally you would expect Unix filespecs but in case of e.g. "foo.c.getopt"
> is recognised as a RISC OS filespec (so copy_or_null() is called) because
> "c" is in the sfix list.
> Although the user is helped with a careful sfix choice for his particular
> CVS project, the analysis of the problem is far from logical (why is
> ".new.msg.1.f.v" is Unix filespec and "msg.1.f.v" a RISC OS filespec ?
> I'm taking a real life example here).

Why is there a dot preceeding the 'v' ? Isn't is supposed to be a comma?

> So I would like to ask if there is any objection to have a
> __riscosify_control bit allocated which, if set, redirects guess_or_null()
> straight to translate_or_null().  Default I would leave it unset, so that
> current heuristic behaviour remains as it is.
> Objections ?

None from me.


Nick Burrett
Network Engineer, Designer Servers Ltd.   http://www.dsvr.co.uk

More information about the gcc mailing list