I have now begun examining the source of the csh implementation and it does not look too bad.
The thing that struck me, however is that we might wish to split the mailinglist in two - one for project related discussion and one for development discussion. The risk is of course that one of the lists will stagnate, but the risk of not doing so is to flood this list with messages which are largely irrelevant to any non-programmer. (But perhaps this will make everyone feel more "in the know"?)
Well, we can discuss this on _monday_ :-) I just thought I would mention it so people have time to think about it.
Now on to the csh status:
1) The issue of csh using SAS/C internal structures seems to be possible to work around using a combination of NameFromFH() or ExamineFH() with freopen(). Possibly there might be some problem if there is a file handle which does not have a name. (Does anyone know is this is so? E.g. will NameFromFH(pr_COS) return "CONSOLE:" on OS4 if called with the default pr_COS of a DOS process run from shell?)
2) Rewriting the internal command handling to accept unix-style paths seems easy enough, though it will take some time to do.
3) There is be a bunch of other dependencies, but most seem minor and should be possible to work around using standard C and AmigaOS 3.1 code.
My working plan for now is to continue using SAS/C while removing all obvious incompatibilities and then move the code to gcc to see what further issues pop up.
-Peter aka. Archprogrammer
Reality is for people who cannot face ScienceFiction. Only lefthanded people are in their right minds.