have you noticed 6.0 changes to _STRICT_?

[naglists]

I stumbled across some code, or one of my authors did, that is behaving
differently in 6.0 than in 5.3.

In 5.3, a package with _STRICT_=1 operates "silently" but in 6.0 the debug
window opens and displays warnings regarding the implicit declaration of
variables. The 6.0 behavior seems, actually, to be correct, but I can't
quite figure out why it is behaving differently than 5.3.

At this point, not a biggee, just a curiosity.

--
Paul Nagai

[ssauvage]

Hello Paul.

I have encountered the same behaviour, and it appears that with 6.0, use of _STRICT_ variable leads ... to a strict result.
In 5.3, undeclared variables were not really well detected. This appears to be corrected with 6.0.
From my point of view, it is a good thing as it improves custom code reliability.
Regards,

Sébastien


Le 13/07/2012 00:00, Paul Nagai a écrit:

I stumbled across some code, or one of my authors did, that is behaving differently in 6.0 than in 5.3.

In 5.3, a package with _STRICT_=1 operates "silently" but in 6.0 the debug window opens and displays warnings regarding the implicit declaration of variables. The 6.0 behavior seems, actually, to be correct, but I can't quite figure out why it is behaving differently than 5.3.

At this point, not a biggee, just a curiosity.

--
Paul Nagai






Site Links: View post online View mailing list online Send new post via email Unsubscribe from this mailing list Manage your subscription


Use of this email content is governed by the terms of service at: