17 May 96 09:51, Peter Collis wrote to andrew clarke:

 ac>> I should think so, as the two versions of the code are effectively
 ac>> the same as far as any ANSI/ISO C compiler should be concerned.  I
 ac>> wouldn't recommend running it though.  :-)

 > Well moving an unknown source to an unknown destination would sure make
 > for some interesting results :-), I thought the question was more to do
 > with having to cast the return from strcpy() to void to stop the compiler
 > generating a warning, i just commented that QC doesn't require the void
 > cast even at the highest warning level.

Right, and nor do any of the other compilers I have here.  Nor does C-Lint.

What I was hoping to find out was the purpose of the numerous casts of
function returns to void [eg. (void) sprintf(xxx, ...);] in the BinkleyTerm
2.60 source code.  More specifically, which compilers generate warnings
without the cast (keeping in mind that the official distribution of
BinkleyTerm are compiling the DOS, OS/2 and Windows NT versions with just
two compilers - MS Visual C++ and IBM CSet/2++), what the reason for the
warning was and therefore find out why the warning was issued.

I canna find any logical explanation for any of it cap'n.  ;-)

Having only limited success with the Bink developers themselves I thought I
might take a shot in the dark and post a more generic query in AUST_C_HERE.

I'll hide under my rock now.

;-)

Regards
Andrew

--- Msged/2 3.36ac alpha 1