[B136] Error loading Mastering ENVY/Developer Testing Extensions

VA Smalltalk is a "100% VisualAge compatible" IDE that includes the original VisualAge technology and the popular VA Assist and WidgetKit add-ons.

Moderators: Eric Clayberg, wembley, tc, Diane Engles, solveig

[B136] Error loading Mastering ENVY/Developer Testing Extensions

Postby marten » Fri Feb 19, 2010 5:23 am

I got an error under Linux (did not check Windows):

Mastering ENVY/Developer Testing Extensions V 5.5.1 [19] can not be loaded, because MedPrereqCheckTestCase>>#quonk does not compile.
Marten Feldtmann, Principal Smalltalk User, Private
SkypeMe callto://marten.feldtmann
marten
[|]
 
Posts: 641
Joined: Sat Oct 14, 2006 7:10 am
Location: Hamburg - Germany

Re: [B136] Error loading Mastering ENVY/Developer Testing Extens

Postby wembley » Fri Feb 19, 2010 6:00 am

Marten -

You will get the same error in Windows. This code has not changed since we introduced it in VAST V7.5. I do not remember seeing this error before (but that could be due to a memory fault). We will look into it. Case 45357.
John O'Keefe [|], Principal Smalltalk Architect, Instantiations Inc.
wembley
Moderator
 
Posts: 405
Joined: Mon Oct 16, 2006 3:01 am
Location: Durham, NC

Re: [B136] Error loading Mastering ENVY/Developer Testing Ex

Postby wembley » Fri Feb 11, 2011 7:17 am

Fixed in V8.0.4.

The behavior differs based on whether or not you are running with a clean image. In a clean image, the 2 symbols are not defined, so you get the compiler error; otherwise, the 2 symbols already exist, so you get only the 2 Warning 91 messages.

There is no way to eliminate the 2 Warning 91 messages on first load since the test case is intended to define 2 globals in the unmanaged namespace. But if you do a reload of the application (without an intervening unload) the 2 globals will already be defined, so you will not get the 2 Warning 91 messages. The best that can be done is write an explanation to the Transcript that covers both cases.

I also discovered that the app did not remove the 2 globals when it was unloaded -- this has been corrected.

Finally, I renamed the 2 globals to something more unique to eliminate the possibility of naming collisions.
John O'Keefe [|], Principal Smalltalk Architect, Instantiations Inc.
wembley
Moderator
 
Posts: 405
Joined: Mon Oct 16, 2006 3:01 am
Location: Durham, NC


Return to VA Smalltalk 7.0, 7.5 & 8.0

Who is online

Users browsing this forum: Yahoo [Bot] and 1 guest