Misuse of "signed char* OUTPUT"

[GoogleCodeExporter]

signed char* OUTPUT passes single chars, not strings. Audit the following
methods for string passing

H5Apublic_wrap.i:415:%apply signed char* OUTPUT{char* buf}
H5Fpublic_wrap.i:437:%apply signed char* OUTPUT {char* name}
H5Gpublic_wrap.i:174:%apply signed char* OUTPUT {char* buf};
H5Gpublic_wrap.i:337:%apply signed char* OUTPUT {char* buf};
H5Ipublic_wrap.i:177:%apply signed char *OUTPUT {char* name}
H5LTpublic_wrap.i:214:%apply signed char* OUTPUT {char* buffer}
H5LTpublic_wrap.i:316:%apply signed char* OUTPUT {char* buffer}
H5LTpublic_wrap.i:645:%apply signed char* OUTPUT {char* data}
H5LTpublic_wrap.i:662:%apply signed char* OUTPUT {char* data}
H5LTpublic_wrap.i:680:%apply signed char* OUTPUT {unsigned char* data}
H5Ppublic_wrap.i:913:%apply signed char* OUTPUT {char* name}
H5Tpublic_wrap.i:279:%apply signed char* OUTPUT {char* oname}

Original issue reported on code.google.com by solomon....@gmail.com on 16 May 2008 at 11:07

[GoogleCodeExporter]

Original comment by solomon....@gmail.com on 16 May 2008 at 11:07

• Added labels: Milestone-Release1.0

[GoogleCodeExporter]

Started fixing as unit tests are implemented.

Original comment by solomon....@gmail.com on 29 Dec 2008 at 9:07

• Changed state: Started

[GoogleCodeExporter]

Fix is known, and no need to keep this open even though some source still needs 
to be
updated.

Original comment by solomon....@gmail.com on 31 Jan 2009 at 11:58

• Changed state: Fixed