Author larry
Recipients Claudiu.Popa, larry, michael.foord, ncoghlan, terry.reedy, yselivanov
Date 2014-01-19.10:44:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390128283.34.0.158345143237.issue17481@psf.upfronthosting.co.za>
In-reply-to
Content
I just want to mention, while we're all thinking about this stuff: I plan to enhance the Signature object to reflect "optional groups".  Right now Signature objects cannot express parameters that are optional but don't have a published default.  (e.g. a string parameter for a builtin having a default of NULL).  A lot of these are being converted using optional groups, and I want to make it at least possible for user code to introspect those functions and understand that those are optional parameters.

My original plan was to add a "group" member, containing an arbitrary identifier of the "group" this parameter belongs to.  I'm not sure that's sufficient; I may also need a "parent_group" parameter, or something like that, to represent the group that this group is nested in.  I'm still thinking about it.  But I'm hoping to get to this in the next two or three days.
History
Date User Action Args
2014-01-19 10:44:43larrysetrecipients: + larry, terry.reedy, ncoghlan, michael.foord, Claudiu.Popa, yselivanov
2014-01-19 10:44:43larrysetmessageid: <1390128283.34.0.158345143237.issue17481@psf.upfronthosting.co.za>
2014-01-19 10:44:43larrylinkissue17481 messages
2014-01-19 10:44:43larrycreate