[BUG] Incorrect moduleName when translating external
plugin on Win32
Bob Hartwig
bob at bobjectsinc.com
Tue Feb 6 00:40:58 UTC 2001
That's my problem; I forgot to copy the new VM over to this particular
directory. Sorry for the false alarm.
-Bob
At 04:03 PM 2/5/2001 -0800, you wrote:
>Bob,
>
>Are you using the latest 3.0alpha1 VM?! What you're reporting sounds as if
>you are using some outdated VM. Please make sure you haven't accidentally
>associated the .image with an older VM. The way to find out is press F2 and
>then choose "display version information". What it should say is that it's a
>"Squeak 3.0 VM (alpha build 1)".
>
>Cheers,
> - Andreas
>
>> -----Original Message-----
>> From: Bob Hartwig [mailto:bob at bobjectsinc.com]
>> Sent: Monday, February 05, 2001 4:00 PM
>> To: squeak at cs.uiuc.edu
>> Cc: recipient list not shown
>> Subject: Re: [BUG] Incorrect moduleName when translating
>> external plugin
>> on Win32
>>
>>
>> Thanks for the info Tim,
>>
>> >
>> >If you look at Smalltalk listLoadedModules or Smalltalk
>> >listBuiltinModules you will see that the date and (i) or (e) is
>> >included.
>> >
>>
>> Smalltalk listLoadedModules gives a primitive failure in Squeak 3.0 on
>> Win32. It sounds like I should rephrase my bug report:
>>
>> In Squeak 3.0 on Win32, external plugins immediately report primitive
>> failures if the generated C file has a properly formatted moduleName
>> string, eg:
>>
>> const char *moduleName = "ExamplePlugin 5 February 2001 (e)";
>>
>> Only by editing the line to:
>>
>> const char *moduleName = "ExamplePlugin";
>>
>> or removing the line entirely, will the primitive failures go away.
>>
>
>
>
More information about the Squeak-dev
mailing list
|