What is the differenct between FindClass() and FindContextClass()?
The documentation for FindClass() says: Locates a Class object in the current
thread context.
The documentation for FindContextClass() says: Locate a Class object in the
current Method or
Routine Package context.
Both
FindClass is a thread context API, which is invoked outside of the context
of any running code. As such, it is limited to locating those classes that
are provided by the system (i.e., in .environment). FindContextClass
performs the same sort of search that would occur in any piece of Rexx code
On 31.07.2014 13:44, Rick McGuire wrote:
FindClass is a thread context API, which is invoked outside of the context of
any running code.
As such, it is limited to locating those classes that are provided by the
system (i.e., in
.environment). FindContextClass performs the same sort of
Hmm, went thru the source code to find all FindClass() usages to check them out.
There is one case where AttachThread() - returning a thread context - is used
and where FindClass()
would find a context class (one that is definitely not in .environment). Not
sure why, not sure
whether an error
What part of I do not investigate problems without a bug report and a
means of reproducing the problem are you not understanding.
Rick
On Thu, Jul 31, 2014 at 9:27 AM, Rony G. Flatscher rony.flatsc...@wu.ac.at
wrote:
Hmm, went thru the source code to find all FindClass() usages to check
Just took a peek at the code and FindClass() searches both .local and
.environment. My guess is you added that class to .local somewhere.
Rick
On Thu, Jul 31, 2014 at 9:27 AM, Rony G. Flatscher rony.flatsc...@wu.ac.at
wrote:
Hmm, went thru the source code to find all FindClass() usages to
On 31.07.2014 15:52, Rick McGuire wrote:
Just took a peek at the code and FindClass() searches both .local and
.environment. My guess is
you added that class to .local somewhere.
Well, I double-checked on that already, hence I will file a bug and upload the
sources with the 32-
and 64-bit
