On Thu, Apr 06, 2017 at 04:41:38PM +0200, Jan Tulak wrote: > Followup of my "[xfsprogs] Do we need so many data types for user input?" email. > > In the past, when mkfs was first written, it used atoi and > similar calls, so the variables were ints. However, the situation moved > since then and in course of the time, mkfs began to use other types too. > > Clean and unify it. We don't need negative values anywhere in the code and > some numbers has to be 64bit. Thus, uint64 is the best candidate as the target > type. I'm with Darrick and Eric on this - it's not the right conversion to make for all the reasons they've pointed out. Further, I think it's the wrong direction to be working in. What I originally intended the config option table to be used for was to /replace all these config variables/ with config option table lookups. We don't need tens of variables to say we certain options set - once option parsing is complete we can just lookup the config table and use the option value directly. i.e. we need to work towards removing all the variables, not try to make them pretty.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
