Would it be possible to make *zfs_prop_get_type* public in a future release? We already have a number of property helper functions exposed, but not this one. Thanks, -- Ian.
On 21/07/2010 11:20, Ian Collins wrote:> Would it be possible to make *zfs_prop_get_type* public in a future > release? We already have a number of property helper functions exposed, > but not this one.There are no Commited (ie Public) documented interfaces for libzfs at all. I think what you mean is that the zfs_prop_get_type function is scoped as local rather than global. Just because it has global scope doesn''t mean it is a "Public" ie documented and stable interface (Committed in the ARC terminology). Why do you need it ? -- Darren J Moffat
On 07/21/10 10:38 PM, Darren J Moffat wrote:> On 21/07/2010 11:20, Ian Collins wrote: >> Would it be possible to make *zfs_prop_get_type* public in a future >> release? We already have a number of property helper functions exposed, >> but not this one. > > There are no Commited (ie Public) documented interfaces for libzfs at > all. I think what you mean is that the zfs_prop_get_type function is > scoped as local rather than global. Just because it has global scope > doesn''t mean it is a "Public" ie documented and stable interface > (Committed in the ARC terminology). >I appreciate the difference.> Why do you need it ? >I have an application that wraps libzfs and it''s a missing piece in the jigsaw. I can map a zfs_prop_t to the property''s name with zfs_prop_to_name, but not to its type. -- Ian.
On 21/07/2010 12:17, Ian Collins wrote:> On 07/21/10 10:38 PM, Darren J Moffat wrote: >> On 21/07/2010 11:20, Ian Collins wrote: >>> Would it be possible to make *zfs_prop_get_type* public in a future >>> release? We already have a number of property helper functions exposed, >>> but not this one. >> >> There are no Commited (ie Public) documented interfaces for libzfs at >> all. I think what you mean is that the zfs_prop_get_type function is >> scoped as local rather than global. Just because it has global scope >> doesn''t mean it is a "Public" ie documented and stable interface >> (Committed in the ARC terminology). >> > I appreciate the difference. > >> Why do you need it ? >> > I have an application that wraps libzfs and it''s a missing piece in the > jigsaw. I can map a zfs_prop_t to the property''s name with > zfs_prop_to_name, but not to its type.All I can suggest is log a CR at bugs.opensolaris.org and maybe someone will be kind and change the scope but I doubt it would be high priority given that libzfs is not documented and doesn''t have a public interface taxonomy. Maybe if you provided the fix via the ON request-sponsor facility it might get done. -- Darren J Moffat
On 07/21/10 11:27 PM, Darren J Moffat wrote:> On 21/07/2010 12:17, Ian Collins wrote: >> On 07/21/10 10:38 PM, Darren J Moffat wrote: >>> On 21/07/2010 11:20, Ian Collins wrote: >>>> Would it be possible to make *zfs_prop_get_type* public in a future >>>> release? We already have a number of property helper functions >>>> exposed, >>>> but not this one. >>> >>> There are no Commited (ie Public) documented interfaces for libzfs at >>> all. I think what you mean is that the zfs_prop_get_type function is >>> scoped as local rather than global. Just because it has global scope >>> doesn''t mean it is a "Public" ie documented and stable interface >>> (Committed in the ARC terminology). >>> >> I appreciate the difference. >> >>> Why do you need it ? >>> >> I have an application that wraps libzfs and it''s a missing piece in the >> jigsaw. I can map a zfs_prop_t to the property''s name with >> zfs_prop_to_name, but not to its type. > > All I can suggest is log a CR at bugs.opensolaris.org and maybe > someone will be kind and change the scope but I doubt it would be high > priority given that libzfs is not documented and doesn''t have a public > interface taxonomy. Maybe if you provided the fix via the ON > request-sponsor facility it might get done. >OK thanks, I''ll follow it up. -- Ian.