Re: Returning a pointer (was - parameters - const, value, reference)

Peter Connell wrote:
> 
> You may be a little surprised (but then again not) that one of the unwise 
> practices here is that someone discovered that they could avoid unreferenced 
> pointer exceptions to unpassed parameters by actually coding a PLIST within 
> the called procedure that redeclares the parameters declared in the procedure 
> interface (get that).
> ...

Nope, I don't get it - could you show an example?  But ask them why they
think it's a good idea to use the value of an unpassed parameter, even
if they can do so somehow without getting an exception.  Ask them if
they would use that trick in their payroll software:

  your_pay = your_pay - maybe_unpassed_parm1 * maybe_unpassed_parm2