×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
It's been like this since V5 at least, probably since the beginning. Saw an
explanation once, probably on this list, but I've slept a few hundred times
since then.
Dave Shaw
Mohawk Industries
----- Original Message ----
From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
To: Wdsci-L <wdsci-l@xxxxxxxxxxxx>
Sent: Tue, April 10, 2012 4:39:07 PM
Subject: [WDSCI-L] No variables "visible" while in subroutine
This may have been the "way it is" forever and I just don't use subroutines
enough to have noticed but ...
Student noticed today that when they were in a subroutine all of the variables
in the view disappeared, replaced by a message to the effect that no variables
were defined at this level. In other words much what you'd see in a subproc with
no variables defined. By clicking on the PEP entry in the call stack they could
see and modify the variables, but not without taking action and not if the
_actual_ call stack entry was highlighted.
Is this rather odd behaviour new or ... ??
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
