cc 5.88: Unix-y include paths on the command line
Stuart Swales (8827) 1323 posts |
I may be having brain fade but didn’t
where c.foo does The Acorn C/C++ manual suggests that it is supposed to in the section on Include files where it talks about filename translation for
does, of course, work. |
Rick Murray (539) 13747 posts |
Talking of weird/changed behaviour with filenames… ObjAsm was fiddled with1 in 2019. Had to fix all of my MakeFiles to get stuff working again. 1 Polite way of saying “broken”. |
Steve Pampling (1551) 8125 posts |
. Talking of weird/changed behaviour with filenames… ObjAsm was fiddled with1 in 2019. Had to fix all of my MakeFiles to get stuff working again One could of course regard the change as a move to a standard, which required users to remove the sticking-plaster modifications :) |
Rick Murray (539) 13747 posts |
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. |