Peter Naulls wrote:
Duncan Moore wrote:
I was expecting/hoping that both files would be filetyped as Pdf. The
reason is that if I write a program that I want to use Unix format
filenames, I unset __RISCOSIFY_NO_PROCESS and I get automatic
filetyping of newly created files. On the other hand, if I want the
program to use RISC OS format filenames, I set
__RISCOSIFY_NO_PROCESS, but then I don't get the automatic
filetyping, which seems inconsistent.
But again, this is exactly consistent. The filetype is part of the
processing that you've just completely turned off with that flag.
Yes, I agree that the result is exactly consistent with the coding logic.
What I was getting at is that the act of selecting RISC OS names (in such a
way that they can be used in a convenient manner) precludes the ability to
have automatic filetyping - yet there's no intrinsic reason why looking at
an extension and setting a filetype should apply to Unix format names only.
I thought I may have been overlooking something, but it seems that I wasn't.
Is there some other way of getting automatic filetyping of files if I
want a program to use RISCOS format filenames?
Yes, but it does seem a little like you didn't read all my response,
and the suggestion I already implied :-( It should be obvious, if
not entirely convenient, that what you want to do is turn off all the
other flags except the filetype one. Although, again I cannot promise
that that will work, due to it really being oriented towards unix
names.
Yes, it's obvious that's what you implied. I was asking if there's an an
alternative to this obvious, but 'not entirely convenient', way of doing it.
No one has suggested an alternative, so it look's like there isn't one.
Thanks for your help
_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
