🚀 go-pugleaf

Thomas A. Stolz wrote:
 > 
 > Several of my coworkers have recently brought to my attention published code
 > which always casts unused return values to (void).  For example, this code
 > would use the statement:
 >         (void)strcpy( dest, src );
 > rather than the statement:
 >         strcpy( dest, src );
 > I see no advantage in using the cast.  In fact, I would tend to believe it
 > would make the code harder to read, especially for inexperienced programmers.


If used consistently, then I can get used to the style of coding where one
constantly "disposes" of a returned value by casting to void.   It's certainly
an education for the unexperienced in such a style (but a trivial technique to
learn).

The main reason I've seen programmer's use this style is to quiet the "lint"
checkers.   I don't naturally code this way, but can certainly read code in
this style without losing comprehension.