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

[Andreas K. <and...@Ac...>]

> Here's the warnings that were mentioned:

> 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.

Yep, some (sub)section tiltes are not unique ... Minor thing. I defered that
to after the release.


> 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

Known bug with handling of integer numbers in the 8.5 core. This might be
gone now, with the bignum processing merged into the head.

>
> ==== 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

tcl_precision differences

> 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.

No, these are the floating point elements which differ.


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

Arjen knows about it, is waiting for the head to stabilize a bit more in the
number area.

>
>
>
> 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

Yup, because parts of clock are now procedures.

> - 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
> TlRMTVNTUAADAAAAGAAYAGoAAAAYABgAggAAAAwADABAAAAACAAIAEwAAAAWABYAVA
> AAAJoAAAABAgAAAAAAAABE
> AE8ATQBBAEkATgB1AHMAZQByAFcATwBSAEsAUwBUAEEAVABJAE8ATsM3zVy9RPyXgq
> Znr21CfG3mfCDC0+d8VoLTft
> Hx9ZaM2NlnEeJBCjvPm4ryx3aR4A==
> ---- Result should have been (exact matching):
> 0
> TlRMTVNTUAADAAAAGAAYAGoAAAAYABgAggAAAAwADABAAAAACAAIAEwAAAAWABYAVA
> AAAJoAAAABAgAAAAAAAEQA
> TwBNAEEASQBOAHUAcwBlAHIAVwBPAFIASwBTAFQAQQBUAEkATwBOAMM3zVy9RPyXgq
> Znr21CfG3mfCDC0+d8ViWpjB
> wx6BhHRmspst9GgPOZWPuMITqcxg==
> ==== SASL-NTLM-1.1 FAILED

For Pat, no idea.


> So, the worst failure was in the first module, where the new resolution

No, not the resolution, these are integer numbers, not floating point. At
the time this was found we found that the integer numbers in Tcl 8.5 had a
serious bug.

> is causing a lot of test result failures.  I suspect a number of the
> other failures are similar.

But most others are something with changes in floating point precision


--
	Andreas Kupries <and...@Ac...>
	Developer @ http://www.ActiveState.com, a division of Sophos
	Tel: +1 604 484 6491