RE: Strange behavior w/%editc()

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: James Rich
>
> What is A?  What is B?  How will moving A to B affect B?  Does A contain
> valid data for the data type of B?  The first method answers all these
> questions.

So does looking at a compiler listing.  Or a D-spec.  This "benefit" of
being able to tell the length and width of every affected field by looking
at a single source statement is overvalued at best.  Sure, it's nice for my
mom to be able to look at my source code and tell what it's doing, but is it
necessary?  Heck no.  And certainly not at the cost of a lot of really
redundant coding.  If I wanted that, I'd use COBOL.

If you want to type all that extra syntax, be my guest.  But I'd caution you
against trying to make it a standard in any development department I've ever
worked for.  The maintenance programmers will run you out of town.

Joe