BIND 10 #284: Not every 'data' parsing is done with json
BIND 10 Development
do-not-reply at isc.org
Mon Jul 19 22:13:59 UTC 2010
#284: Not every 'data' parsing is done with json
-------------------------------+--------------------------------------------
Reporter: jelte | Owner: jelte
Type: defect | Status: reviewing
Priority: minor | Milestone: 06. 4th Incremental Release
Component: Unclassified | Resolution:
Keywords: | Sensitive: 0
Estimatedhours: | Hours:
Billable: 1 | Totalhours:
Internal: 0 |
-------------------------------+--------------------------------------------
Changes (by jinmei):
* owner: jinmei => jelte
Comment:
Replying to [comment:4 jelte]:
> > - not necessarily for this changeset, but I personally see read(-1)
> > rather confusing. Wouldn't it be clearer to pass nothing to
> > read()? Or at the risk of looking redundant we might define a
> > constant such as READ_EVERYTHING = -1 and pass it to read()
>
> oh, yes, no argument is ok too, and more clear
>
There's one more occurrence of read(-1) in r2532. I removed it and
committed the change to the branch (r2534).
Other changes look okay.
--
Ticket URL: <http://bind10.isc.org/ticket/284#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list