In article . com,
"Harlan Grove" wrote:

If clarity of code were important, we wouldn't be using spreadsheets.

OK, you've got me there...

As for specificity, if the default value is well-defined (which it is),
there's nothing gained by including the default value of the 4th arg.
Of course, you may be using a different definition of 'specificity'.

Specificity in this case only meaning completely specifying the
arguments. Yes the fourth argument's default case is well defined, but
for me it's a habit that prevents errors. It indicates that the choice
of approximate or exact match has been explicitly made. Makes
troubleshooting easier, too - I don't have to question whether the
argument was inadvertently left out, or if an approximate match was
intended.

What's gained by leaving it out, other than a few keystrokes?

Compatibility with other spreadsheets, FWLIW these days. Also, omitting
default arguments reduces file size. And, in extreme cases, it's
necessary to do so in very long formulas in order to remain under
Excel's formula length limit.

Valid points. In my case, however, I don't have any clients that know
enough about other spreadsheets that would make this a problem, nor do I
typically do enough VLOOKUPS to make the extra bytes an issue. I don't
remember if the TRUE/FALSE is tokenized or not...

I also try hard not to have very long formulae - they're hell to
maintain, especially 6 months or more after delivery.

Besides, the more keystrokes there are, the more opportunities there
are for tpyos.

<g