[squeak-dev] FFI issue in Squeak 4.2 ?

Levente Uzonyi leves at elte.hu
Tue Feb 22 05:25:55 UTC 2011


On Mon, 21 Feb 2011, Chris Muller wrote:

>> Yes. I hacked together a basic Metacello configuration for Xtreams, which
>> automatically loads FFI if the Xtras package is requested (and FFI is not
>> loaded) and fixes the underscore problems for Squeak. I uploaded it to the
>> MetacelloRepository (http://squeaksource.com/MetacelloRepository ). You can
>> load Xtreams into Squeak 4.2 with it using the following script:
>>
>> Installer ss
>>        project: 'MetacelloRepository';
>>        install: 'ConfigurationOfXtreams'.
>> (Smalltalk at: #ConfigurationOfXtreams) perform: #loadBleedingEdge
>
> Hi, can you clarify whether this loads a fixed-configuration or a
> variable configuration?

"baseline" and "version" are Metacello terms. A "baseline" specifies a 
set of packages and their dependencies. A "version" defines which version 
of those packages should be loaded. So this loads the latest version of 
all packages. So this script is the "head" on SqueakMap.

>
> I will document this in SqueakMap, but I think it's important to know
> whether this "configuration" is a true configuration or if it's a
> load-script that fetches the latest-and-greatest?  #loadBleedingEdge
> suggests the latter, and, if so, would you also specify a load-script
> that will ensure longevity in Squeak 4.2?

The latest version of the packages can be considered as stable, all tests 
pass. I can create a "version" with these and mark it as stable for 
Squeak 4.2. When this is done, a different script can be added for 4.2 on 
SqueakMap.


Levente

>
> I think we should be explicit about load-scripts kept in Metacello,
> like we are now doing in SM, and say, "you can load the 'latest
> bleeding-edge' Xtreams code with the following script" rather than
> saying, "into Squeak 4.2" because there is no guarantee that will
> remain the case.
>
> Thanks and Regards,
>  Chris
>
>
>
>>
>> The Pharo version of this script should use Gofer instead of Installer to
>> load the configuration itself, but the last line should remain the same.
>>
>> There are no versions yet, just a baseline, so one can only load the
>> #bleedingEdge versions of the packages. This is equivalent with the current
>> loader scripts.
>>
>> I also defined some groups which only load some, but not all packages (no
>> tests, no Xtras, etc). See the commit message or the specification itself
>> for details.
>>
>>>
>>>> I managed to load XTreams to Squeak Trunk (possibly works with 4.2 too)
>>>> using the following script:
>>>> ...
>>>> I also uploaded a new version of Xtreams-Xtras to the repository which
>>>> fixes XTHMACTest and XTHashTest for Squeak.
>>>>
>>>> With these changes, all tests are green on Windows.
>>>
>>> Excellent! So that means the new Bcrypt based hashing worked for you too.
>>> Thank you very much! I really appreciate your help.
>>
>> Yes. Before XP users start wondering why this doesn't work for them, bcrypt
>> is only supported on Vista and later versions (according to msdn).
>>
>>
>> Levente
>>
>>>
>>> Martin
>>>
>>
>>
>


More information about the Squeak-dev mailing list