On Thu, Jul 30, 2009 at 04:08:43PM +0200, Karel Zak wrote:
> On Mon, Jul 20, 2009 at 12:32:44AM +0200, Christoph Hellwig wrote:
> > I'm not entirely sure how such APIs would fit into the blkid library
> > design.
>
> I have extended the low-level API to better fit to all future
> requirements (topology and partitions probing).
>
> The probing functions are organized in separate "chains". Currently
> the library supports superblocks, topology and partitions chains.
It seems that the chains abbreviations: "sublks", "toplgy" and
"parts" are too unreadable for some people. I'll probably use full
names for the API:
BLKID_CHAIN_SUPERBLOCKS
BLKID_CHAIN_TOPOLOGY
BLKID_CHAIN_PARTITIONS
any objections?
Frankly, I have problem to select good names for symbols:
blkid_probe_chain_enable_binary;
blkid_probe_chain_filter_types;
blkid_probe_chain_filter_usage;
blkid_probe_chain_invert_filter;
blkid_probe_chain_reset_filter;
blkid_probe_chain_set_flags;
blkid_probe_lookup_ullong_value;
blkid_probe_lookup_ulong_value;
looks too long for my... any suggestion?
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
