Re: About conversions

[Ted Dennison <dennison@telepath.com>]

In article <8vept5$814$1@nnrp1.deja.com>,
  Robert Dewar <robert_dewar@my-deja.com> wrote:
(talking about converting actual "out" parameters)
> If you use this feature, you will most definitely confuse
> the reader, especially in the case of an out parameter,
> precisely because the syntax is so confusing. Note that

To the reader, it doesn't look any different than the conversion of an
"in" parameter. They have to go to the subprogram declaration to even
see what the mode is. Prohibiting conversions for "out" but allowing it
for "in" would just be an extra (also confusing) rule for developers to
remember about when its allowed and when it isn't. Plus it would cause
the extra source code previously mentioned to create the new temp
variable. Tracking that down and making sure its handled right before
and after the call is just going to be more extra work for maintainers.

You do have a point about it being confusing to some beginners. I'd
imagine its particularly bad for those who are comming from another
language that doesn't allow this kind of thing. But I don't think you
can say that its an inarguable maintanence problem. It can be argued
either way.

--
T.E.D.

http://www.telepath.com/~dennison/Ted/TED.html


Sent via Deja.com http://www.deja.com/
Before you buy.