Mark Hindess wrote:
I plan to modify the hythread api so that it uses "const char*" for
names of threads and monitors rather than the current "char*". Since
the former is more appropriate and avoids errors (when using const
strings) without appropriate casts on recent versions of gcc. (For
instance, you can't build the federated build with -Dhy.no.thr=true
with recent versions of gcc because of a warning treated as an error in
jdktools/modules/jpda.)
+1 - I fixed a few of these a while back where I got compiler warnings.
const char * is the appropriate type for these, as you say.
Regards,
Oliver
I don't think this should cause any issues are implicit casting in the
other direction is permitted without any warning/error.
Regards,
Mark.
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
