On Fri, Aug 15, 2014 at 5:12 PM, Denys Vlasenko <vda.li...@googlemail.com> wrote:
> On Fri, Aug 15, 2014 at 3:11 PM, <lp...@archlinux.us> wrote: > >> Applets are defining the help display text on their own, and it is >> different for different applets. >> > Also, it will be difficult to change at many places if you happen to need >> to.. >> > centralization would rock here imho... >> > > Centralization used to "rock", when all help texts > were in include/usage.src.h (then named include/usage.h). > > It was easy to see all help texts in one place, but it was > a complete nightmare to keep applet and its help text in sync: > you needed to jump between two different files > in order to check what every option does in code, > and what help text says. > > People were routinely forgetting to update help text, > because it was in separate file. > > Adding new applet needed editing many files. > > You can see all help texts in one place after a build: > it's in generated file, include/usage.h; > or you can just run auxiliary executable: applets/usage > to have it on stdout. > That is not what I meant. What I meant is centralizing the formatting output. That is, to have some common functions to which you pass your options and the functions will output a standardized format. I did not mean to put all the custom code into one place as a dump. That would be indeed worse than the current, I agree.
_______________________________________________ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
