[net-dns-users] Release candidate for Net::DNS 1.06

[Dick Franks]

On 20 April 2016 at 02:35, Doug Barton <dougb at dougbarton.us> wrote:

> On 04/19/2016 05:16 PM, Dick Franks wrote:
>
>>
>> On 19 April 2016 at 19:58, Doug Barton <dougb at dougbarton.us
>> <mailto:dougb at dougbarton.us>> wrote:
>>
>>     On 04/19/2016 08:39 AM, Dick Franks wrote:
>>
>>     You focused on the wrong part of what I said. Previous to this RC
>>     errorstring was undefined, which allowed me to wrap my previous code
>>     in an 'if (defined ...' block. Now it's defined, but empty (or has
>>     spaces, or doesn't, whatever). That's much worse, as now I have to
>>     do a string compare.
>>
>>
>> We appear to have a problem establishing simple matters of fact.
>>
>
> No, I keep hoping that I don't have to spell out everything in nauseating
> detail. :)
>
> Previously, if there was nothing in errorstring, it was also undefined.



What is there to misunderstand  about "defined"?

I have demonstrated, in nauseating detail as you put it, that errorstring
*IS* defined after axfr() using Net::DNS 1.05.

You have provided not a shred of reproducible evidence to show otherwise.



> Obviously if there is a message there (as both you and I have demonstrated
> to be true in the past) it had to be defined.
>

> The current state with the 1.06-RC is that the field is empty, but the
> variable is defined. That means that I can't just wrap my error-checking
> routine in 'is (defined ...'  I now have to do a string compare. (In fact
> it's worse than that, I have to do both.)  That's bad.
>

ROFL


> Also, you ignored the other issues that I raised in my previous message
> about errorstring. It would be great if you could respond to those as well.


I have better things to do
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/net-dns-users/attachments/20160420/0c422406/attachment.htm>