MIME-Version: 1.0 In-Reply-To: X-Mailer: MIME-tools 5.505 (Entity 5.505) Content-Disposition: inline X-RT-Interface: Web References: <788ba4fd-9fd2-abf0-8512-3539bc9320ab@redhat.com> <1c3fddb0-405f-42dc-95dc-d8c93ca31270@redhat.com> <20160819191948.GA95615@isc.org> Content-Type: text/plain; charset="utf-8" Message-ID: Content-Transfer-Encoding: binary X-RT-Original-Encoding: utf-8 RT-Send-CC: X-RT-Encrypt: 0 X-RT-Sign: 0 Content-Length: 789 > Perhaps we could associate the line number value with it, though, and > pass that to the plugin, so that when the plugin parsed its input it would > have an accurate line number to report when errors were encountered. Turns out this is already doable -- you can get the line number of the bracketed text object by using cfg_obj_line(obj). I think it's only necessary to add a 'lineno' parameter to dns_dyndb_load(). > (If the plugin is parsing its input using libisccfg, then we may need > to update libisccfg so you can set an initial line number. I can't recall > whether such a mechanism already exists.) This mechanism, however, does not yet exist. I'd implement it as a lexer function, isc_lex_setsourceline(), and call that on parser->lexer before calling cfg_parse_buffer().