cc 5.88: Unix-y include paths on the command line

I may be having brain fade but didn’t

cc -c -I../.. foo

where c.foo does #include "whatever.h" that’s on the (Unix-y) include path use to work?

The Acorn C/C++ manual suggests that it is supposed to in the section on Include files where it talks about filename translation for #include "../whatever.h":

In the same way, the lists of directory names given as arguments to the compiler’s Include and Default path SetUp options (see below) are translated to RISC OS format before being used, in the rare event that this is necessary.

cc -c -I^.^ foo

does, of course, work.

Talking of weird/changed behaviour with filenames… ObjAsm was fiddled with¹ in 2019. Had to fix all of my MakeFiles to get stuff working again.
https://www.riscosopen.org/forum/forums/11/topics/13224

¹ Polite way of saying “broken”.

. Talking of weird/changed behaviour with filenames… ObjAsm was fiddled with¹ in 2019. Had to fix all of my MakeFiles to get stuff working again

¹Polite way of saying “broken”.

One could argue that if something has worked for some thirty odd years (going back to Norcroft release 4 at least), then that is the standard and the documentation is what needed to change.

But, then, having the thing be so brain-dead that it translates “s.filename” paths as “blah.s.s.filename” and needs a ^ to get things to work, that to me sounds like the sticking plaster.