>>In my book, the less code... the less errors, the less problems reading the code thus the less problems in resolving errors.
>>
>>Which book did you write? I would love to get a copy :)
>
>You first have to read Dutch :)
>Its really simple. A 20 line routine can contain less errors than a 100 line piece of code. It can be written, read, analyzed and corrected faster.
>
>Seriously, Code Complete written by Steve McConnel would be a good book to start with. Especially the chapters that deal with the code itself (rather than architecture and the process of development), leave clear hints about length of code.
>
>Walter,

A yes and no.

As stated earlier in this thread. 100 lines of simple code could be much easier to maintain then 10 lines of rather complex stuff.

A line coud be very tricky :)

To the example this all starts with. If you do all in C and just call it from from VFP. You have two lines VFP. Is this easier to maintan? Only if there is no problem in the C code ....

:)