Forum OpenACS Development: Re: Unexpected error returned from call to template::element::get_value

Collapse
2: Re: Unexpected error returned from call to template::element::get_value (response to 1)
Posted by Randy O'Meara on 06/22/03 12:37 AM
Tammy, I would vote for catching the error and returning the "implied" empty string as the return value.

I have noticed many times while searching the API docs that programmers seldom explicitly document a proc's return value. To me this is sloppy and leads to many subtle runtime errors.

I would love to see each and every proc documented with a @return property...

Collapse
3: Re: Unexpected error returned from call to template::element::get_value (response to 2)
Posted by tammy m on 06/22/03 01:25 AM
I don't know what's the right way to propose to get something like this into the OACS release code. Maybe it's to submit it as a bug? Anyone have experience with the process?

I agree that it would it clean up some subtle runtime errors in this case fer sure.

thanks.