Igor,
> P.S. The configuration is freshly-baked, i didn't even checked if it
> loads cleanly or not..
> so, i don't recommend updating it in image with your precious code :)
I have tried loading your updated Configuration into Pharo1.4 #14438 and it
loaded ok, but as a NativeBoost beginner it took me sometime to work out
that I needed to run NBFFICallout>>initialize to get the new NB types
registered. I found that this could be achieved using a postLoadDoIt
message in the Configuration ...
spec package: 'NativeBoost-Core' with: [
spec
file: 'NativeBoost-Core-IgorStasenko.75';
postLoadDoIt: #postloadForCore ].
> Gofer it
> squeaksource: 'NativeBoost';
> package: 'ConfigurationOfNativeBoost';
> load.
> (ConfigurationOfNativeBoost project version: '1.4' ) load
> P.P.S. i would really like some help with testing what i did,
> including writing some more tests to cover type system more
> broadly (now since type names follow certain naming rule, many
> different types can be checked without much coding)
Some of the tests failed after the update because it was necessary to
rebuildAccessors for a couple of the structures used so that they referred
to the new NB types.
Although this is a trivial change I would like to try and help your efforts
with some more tests and documentation, but how should I submit them?
Should I follow the "HowToContribute" procedure on the Pharo website?
Thanks, Guy
