Unused variables and bugs

Ola Fosheim Gr via Digitalmars-d digitalmars-d at puremagic.com
Fri Aug 22 21:23:57 PDT 2014


On Saturday, 23 August 2014 at 04:07:58 UTC, ketmar via 
Digitalmars-d wrote:
> On Sat, 23 Aug 2014 03:50:13 +0000
> via Digitalmars-d <digitalmars-d at puremagic.com> wrote:
>
>> - versioning
> refactor it, so that shared code goes to separate functions. 
> nested
> functions especially helpful here. i'm used to this GCC 
> extension.

Won't work. Different versions might need extra parameters, but 
you want the same interface. Like one version might need manual 
calibration.

>> - debugging (commenting out debugging code)
> why comment it out? if (debug_enabled) is fine and can help when
> software fails.

To avoid visual clutter. To be able to span syntactical 
boundaries. To take advantage of hiding in editors.

>> - virtual functions
> they are either abstract or just comment out unused argument 
> names.

No, unused in superclasses, used in subclasses.

>> - future-proof function signatures
> but why? plan your API. if you need to extend it -- add new API 
> calls.

And rewrite all use locations? That sounds like not planning...


More information about the Digitalmars-d mailing list