I've just committed some cleanups and bugfixes
to ncap stuff. The @ handling was not working
with global attributes and now the ncap.in
script is fully parsed again. This is version
2.1.1. I am trying to make a new public release
of this soon.
Compiling and executing ncap on the SGI works
fine but points out some problems with string
parsing and storage. So I've created an ncap-
specific task list in the TODO file. There you
will find the SGI-produced warnings about mixing
char * and unsigned char * types that Linux does
not warn about. We will need to fix these.
Tell me what you suggest for fixing it.
It may require expanding some structures, or
at least doing some typecasting as a band-aid.
I see the mixed-rank stuff has improved, I'm
still not sure under what exact conditions it
fails, but will keep looking as I consider this
the most important remaining problem.
Charlie
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Charlie,
I've had a look at the string errors from the SGI.
Cor ! The SGI compiler is sensitive -It may use signed char as the default for char , I don't know.
I'm reluctant to change "unsigned char *cp" to "char *cp" in the structure ptr_unn as this may cause other problems. So I guess the best thing to do is some typecasting. Possibly you could tackle this as you have access to the SGI machine.
Regards Henry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> I'm reluctant to change "unsigned char *cp" to > "char *cp" in the structure ptr_unn
I agree. Let's work on the more important features
first. BTW, ncap works now on SGI IRIX,IBM AIX,
and Alpha OSF, so it's more or less standards
compliant (or, more likely, the ncap.in test script
should be made more extensive to catch problems).
Also, I've committed many cleanups to ncap in the
past few days, make sure to update before making
changes to the older sources!
Thanks,
Charlie
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've just committed some cleanups and bugfixes
to ncap stuff. The @ handling was not working
with global attributes and now the ncap.in
script is fully parsed again. This is version
2.1.1. I am trying to make a new public release
of this soon.
Compiling and executing ncap on the SGI works
fine but points out some problems with string
parsing and storage. So I've created an ncap-
specific task list in the TODO file. There you
will find the SGI-produced warnings about mixing
char * and unsigned char * types that Linux does
not warn about. We will need to fix these.
Tell me what you suggest for fixing it.
It may require expanding some structures, or
at least doing some typecasting as a band-aid.
I see the mixed-rank stuff has improved, I'm
still not sure under what exact conditions it
fails, but will keep looking as I consider this
the most important remaining problem.
Charlie
Hi Charlie,
I've had a look at the string errors from the SGI.
Cor ! The SGI compiler is sensitive -It may use signed char as the default for char , I don't know.
I'm reluctant to change "unsigned char *cp" to "char *cp" in the structure ptr_unn as this may cause other problems. So I guess the best thing to do is some typecasting. Possibly you could tackle this as you have access to the SGI machine.
Regards Henry
> I'm reluctant to change "unsigned char *cp" to > "char *cp" in the structure ptr_unn
I agree. Let's work on the more important features
first. BTW, ncap works now on SGI IRIX,IBM AIX,
and Alpha OSF, so it's more or less standards
compliant (or, more likely, the ncap.in test script
should be made more extensive to catch problems).
Also, I've committed many cleanups to ncap in the
past few days, make sure to update before making
changes to the older sources!
Thanks,
Charlie