On Sunday 15 November 2009, Michael Bruck wrote:
> >>> The macro is right above the table.
Yep. At least, *now* it's right above.
> >> The problem with this sort of macros is that
... it doesn't really add anything. Even though
it *is* right above that table, you still have to
think more about it than when you see standard
initializer syntax (".field = value,"). The lines
above the top of the table are not necessarily on
the screen, or in your memory.
> >> we have
> >> a dozen targets and having a dozen different
> >> macros gets a bit tedious. The arm11 macros
> >> does show that certain things are tedious in OpenOCD
> >> speak, but hopefully we can address those on
> >> in a more general fashion.
> >
> > This seems highly unlikely, quite a few contributions here lately
> > center around enforcing antiquated bloated syntax.
Instead of "antiquated bloated" I'd say "standard and
universally understood". We're not exactly talking
about a COBOL level of verbosity here. ;)
Did you ever see the original Bourne shell sources?
The ones that abused CPP to make the language look
like Algol-60 instead of C? Now *that* was centered
around enforcing antiquated syntax ...
> > The patch does not
> > improve legibility it merely reflects certain contributer's personal
> > distaste for macros.
>
> This should be contributors', plural is probably warranted here.
It's also a fairly standard policy in most projects:
avoid syntactic sugar macros. To be used, they need
first to be learned ... and that's effort that could
be more usefully applied to other tasks. And to be
used, they also need to be maintained ... likewise.
- Dave
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
