[Plib-users] borland ssg progress??
Brought to you by:
sjbaker
From: Simon <sim...@ho...> - 2003-12-23 20:51:46
|
Hi all, ok I think I'm making progress but I've hit a bump. This is = really a general programming question, throughout ssg you use strrchr. This returns in several forms. The area I'm stuck on now is: =20 return strchr( string, c ); =20 in the mystrchr() method, within ssgParser. The error is to do with converting a const char* to a char*. I've read up on what might be = causing the problem and I think I found it. In the Borland strchr help documentation it specifies the different formats for the command. I extracted the following: =20 char *strchr(const char *s, int c); /* C only */ const char *strchr(const char *s, int c); // C++ only char *strchr( char *s, int c); // C++ only =20 It looks like the usage you've used in ssg is the "c only" one. Is this some funny limitation of the windows version? How can I get around = this? I think once I've fixed this then ssg will compile under Borland. =20 Thanks in advance -simon |