Re: !! Take note !! CVS frozen !! RE: [Tcllib-devel] Tcllib

[Larry W. V. <lv...@ca...>]

Here's the warnings that were mentioned:

Generating /volws/lwv27/ldatae/man/mann/doctoc_api.n
Manpage warning (sectambig): (Sub)Section title "What is a snit::widget?" causes ambiguous
 section references.
Manpage warning (sectambig): (Sub)Section title "What is a snit::widgetadaptor?" causes am
biguous section references.
Manpage warning (sectambig): (Sub)Section title "What is a snit::widget?" causes ambiguous
 section references.
Manpage warning (sectambig): (Sub)Section title "What is a snit::widgetadaptor?" causes am
biguous section references.

Generating /volws/lwv27/ldatae/man/mann/snitfaq.n
Manpage warning (sectambig): (Sub)Section title "What is a snit::widget?" causes ambiguous
 section references.
Manpage warning (sectambig): (Sub)Section title "What is a snit::widgetadaptor?" causes am
biguous section references.
Manpage warning (sectambig): (Sub)Section title "What is a snit::widget?" causes ambiguous
 section references.
Manpage warning (sectambig): (Sub)Section title "What is a snit::widgetadaptor?" causes am
biguous section references.

I have only been using the Tcl 8.5 environment for my testing of
extensions - my users don't want extensions to change on them.
So I have some interesting results using the new tcllib release against
Tcl 8.5. I know this isn't a combo that is particularly expected to be
supported - just thought I'd mention it.

I'm using Solaris 9 on a sparc.


There are 20 tcllib test suite failures.

Module: asn
modules/asn/asn.test
- asn 0.4

==== asn-2.19 integer FAILED
==== Contents of test case:

    binary scan [asn::asnInteger $i] H* result
    list $i [string toupper $result]
    
---- Result was:
8388608 02050000800000
---- Result should have been (exact matching):
8388608 020400800000
==== asn-2.19 FAILED

==== asn-4.19 enum FAILED
==== Contents of test case:

    binary scan [asn::asnEnumeration $i] H* result
    list $i [string toupper $result]
    
---- Result was:
8388608 0A050000800000
---- Result should have been (exact matching):
8388608 0A0400800000
==== asn-4.19 FAILED

plus quite a few more. I won't flood email boxes with them. Just
trying to characterise the types of things that I encountered.

==== counter-avg counter::count FAILED
==== Contents of test case:

    counter::init avg
    counter::count avg 2.2
    counter::count avg 3.3
    counter::count avg 9.8
    counter::get avg -avg

---- Result was:
5.1000000000000005
---- Result should have been (exact matching):
5.1
==== counter-avg FAILED

and a similar failure in counter-hist.

exif-makernote-19.0 makernote field 19 (afpoint) is optional FAILED

The failure occurs in the FocalPlaneXResolution return value - which is now
returning with 7766.9902912621355 instead of the 7766.99029126 previously
returned.  Similar problem appeared with the PlaneYResolution field.
There might be other fields - the output is very long and I wasn't certain
if I was missing a field.

modules/math/fuzzy.test
math::fuzzy 0.2

==== math-fuzzy-ManyCompares-1.1 Compare fails due to missing braces FAILED
:
Removed specific test case to save space here - this isn't a bug
report, just an observation.
:

---- Result was:
1
---- Result should have been (exact matching):
0
==== math-fuzzy-ManyCompares-1.1 FAILED




The profiler 7.2 sortFunctions test failed because the results were returning
with some new elements:

---- Result was:
{::tcl::clock::scan 0} {::tcl::clock::format 0} {::tcl::clock::add 0} {::bar 1} {::foo 2}
---- Result should have been (exact matching):
{::bar 1} {::foo 2}
==== profiler-7.2 FAILED


- SASL::NTLM 1.0.0

==== SASL-NTLM-1.1 NTLM client response FAILED
==== Contents of test case:

    list [catch {
        set ctx [SASL::new -mechanism NTLM -callback NTLMCallback]
        SASL::step $ctx ""
        SASL::step $ctx [base64::decode $Chk(2)]
        set response [SASL::response $ctx]
        SASL::cleanup $ctx
        base64::encode -maxlen 0 $response
    } res] $res

---- Result was:
0 TlRMTVNTUAADAAAAGAAYAGoAAAAYABgAggAAAAwADABAAAAACAAIAEwAAAAWABYAVAAAAJoAAAABAgAAAAAAAABE
AE8ATQBBAEkATgB1AHMAZQByAFcATwBSAEsAUwBUAEEAVABJAE8ATsM3zVy9RPyXgqZnr21CfG3mfCDC0+d8VoLTft
Hx9ZaM2NlnEeJBCjvPm4ryx3aR4A==
---- Result should have been (exact matching):
0 TlRMTVNTUAADAAAAGAAYAGoAAAAYABgAggAAAAwADABAAAAACAAIAEwAAAAWABYAVAAAAJoAAAABAgAAAAAAAEQA
TwBNAEEASQBOAHUAcwBlAHIAVwBPAFIASwBTAFQAQQBUAEkATwBOAMM3zVy9RPyXgqZnr21CfG3mfCDC0+d8ViWpjB
wx6BhHRmspst9GgPOZWPuMITqcxg==
==== SASL-NTLM-1.1 FAILED

==== units-10.1 leading zero is not octal FAILED
==== Contents of test case:

    ::units::convert 09mm meter

---- Result was:
0.009000000000000001
---- Result should have been (exact matching):
0.009
==== units-10.1 FAILED


So, the worst failure was in the first module, where the new resolution
is causing a lot of test result failures.  I suspect a number of the
other failures are similar.  
-- 
Tcl - The glue of a new generation.  <URL: http://wiki.tcl.tk/ >
Larry W. Virden <mailto:lv...@ca...><URL: http://www.purl.org/NET/lvirden/ >
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-