Re: [sv-bc] task/function inout arguments with default values

>From: "Bresticker, Shalom" <shalom.bresticker@intel.com>

>This does not seem quite correct for inouts. For inouts, the actual
>argument needs to be an expression which is valid on the left-hand side
>of a procedural assignment (1364-2005, 10.2.2).

There is another possible way that it could work.  You could consider
that by leaving off the explicit argument value, the user is saying
that they don't care about the value coming back.  They still need to
provide an input value, for the copy-in.  But the copy-out would not
be done.  Therefore the default value expression would not need to be
an lvalue.  Putting it another way, when using the default value for
an inout, it would be treated like an input.

I don't know if that is what was intended.  It seems reasonable, and
more usable than a default that must be an lvalue.  If that was the 
intent, then it needs to say so.

Steven Sharp
sharp@cadence.com