[bind10-dev] [sprint planning] tentative results and discussion for estimates for sprint ending 2012-12-18

[Michal 'vorner' Vaner]

Hello

On Tue, Dec 04, 2012 at 05:30:33AM +0530, Mukund Sivaraman wrote:
> We could accept the trailing comma (bug #2509 comment 1), similar to how
> C compilers accept a trailing comma after a last enum constant when not
> in pedantic mode, so more constants can be added at the end without
> updating the existing lines:
> 
> enum {
>     A,
>     B,
>     C,
> };

I know it might be comfortable (and I do use it in perl a lot, for example). But
in this case, I'd be against doing so even if the parser was our code, which as
was mentioned by others, isn't.

The reason for that is, we use JSON format. The JSON format doesn't allow that.
This allows people to use stock parsers on our configs/other data when they want
to do something (for example examine it for some problems, something like
b10-conf-lint). Changing the format because such a small thing isn't worth it,
the would have to write their own parser (and, no, providing our own parser
isn't solution, such external tools may be written in whatever language the
author likes).

With regards

-- 
The problem with graduate students, in general, is that they have
to sleep every few days.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20121204/3c7455d9/attachment-0001.bin>