You use :optional to denote an optional parameter, and :opt_flag on an
int that is set to "true" if there's a parameter in :optional. The
fact that :opt_flag is optional could be construed to be a bug. But
all tests successful for me now for punie, and fairly quickly, so I'm
going to assume the memory problem's gone.
On Feb 6, 2006, at 11:20 AM, Allison Randal wrote:
On Feb 5, 2006, at 3:05, Leopold Toetsch via RT wrote:
Okay, thanks, changed. Joshua, let me know how it goes. Particle,
could you check and see if this fixes your problem as well?
What's the difference between :optional and :opt_flag? I found a few
lines of documentation on these once I knew what to grep for, but
that's all.
Marking optional parameters is a good move forward. But... retrieving
garbage values into parameters that aren't passed an argument is not a
good design for a stable system. It leads to thorny bugs like this
one. (I've been looking for it for over a month, but could never
reproduce it on any of my machines.) Can you prevent it from
retrieving garbage values, even when :optional isn't set?
Allison
