|
|
|
|
|
|
by MaulingMonkey
3397 days ago
|
|
|
> I'm not a C dev, but is "(null != thing)" still a convention? Configuring the warning your compiler gives for 'if (x=y)' to generate an error instead is a vastly better convention that completely supersedes Yoda style, IMO. 'if ((x=y))' remains available for those who really want to assign in conditionals. |
|
|