time to move to smalltalkhub... On 2012-11-26, at 18:01, Igor Stasenko <[email protected]> wrote:
> indeed, there's a problem.. > something broke MC in my image.. > i have > NativeBoost-Core-IgorStasenko.87 > NativeBoost-Core-IgorStasenko.88 > NativeBoost-Core-IgorStasenko.89 > > in my image, and when i "save" it does not showing any errors.. > > but then no files appear in squeaksource > and more than that, if i trying to open .mcz files in other image, > they fail with errror.. > > something got broken in version history :( > > > On 26 November 2012 21:04, Ciprian Teodorov <[email protected]> > wrote: >> Thanks Igor for pushing the new version of NativeBoost. >> Though, as Guy noted the Core package seems to be missing from squeaksource >> >> -- >> Ciprian >> >> >> On Mon, Nov 26, 2012 at 7:52 PM, Guy Hylton <[email protected]> wrote: >>> >>> Igor, >>> >>> Just looking to check out your and the contributors hard work but >>> ConfigurationOf... refers to "NativeBoost-Core-IgorStasenko.88" which is not >>> found? >>> >>> Guy >>> >>> On Mon, Nov 26, 2012 at 12:41 PM, Igor Stasenko <[email protected]> >>> wrote: >>>> >>>> Hi, there >>>> >>>> i'd like to announce new version of NativeBoost - 1.7. >>>> >>>> Here's an overview of changes comparing to previous version: >>>> >>>> - indirect argument in signatures. >>>> You can now use special syntax to indicate that argument to external >>>> function should be taken from n-th element of variable object (like >>>> Array) >>>> from method's argument or instance variable. >>>> >>>> Syntax: >>>> >>>> myMethod: args >>>> <primitive: .... > >>>> ^ self nbCall: #( void funFoo( int args@1 , float args@2 )) >>>> >>>> Usage: >>>> >>>> self myMethod: { 1 . 1.2 } >>>> >>>> Thanks to Ciprian Teodorov who proposed and implemented it. >>>> >>>> - Win32, features and examples: >>>> >>>> NBWin32Shell - an interface to use windows shell api >>>> (executing commands, showing control panel settings) >>>> >>>> different examples for using HDC, message box etc. >>>> >>>> Thanks to Torsten Bergmann for contribution! >>>> >>>> And last bits, from me: >>>> >>>> A public API changes to avoid use of NBFFICallout global, and instead >>>> use message(s) to denote FFI callout. >>>> >>>> Old syntax: >>>> >>>> NBFFICallout cdecl: #(...) emitCall: [ … ] >>>> >>>> New syntax: >>>> >>>> self nbCallout function: #(…) emit: […] >>>> >>>> >>>> Old syntax: >>>> >>>> NBFFICallout cdecl: #(...) module: .. >>>> >>>> New syntax: >>>> >>>> self nbCallout cdecl function: #(…) module: … >>>> or: >>>> self nbCallout function: #(…) module: … >>>> >>>> because cdecl is default >>>> >>>> Old syntax: >>>> >>>> NBFFICallout cdecl: #(...) module: .. options: #(…) >>>> >>>> New syntax: >>>> >>>> self nbCallout cdecl; >>>> options: #(…); >>>> function: #(…) module: … >>>> >>>> >>>> Old syntax: >>>> >>>> NBFFICallout stdcall: #(...) module: .. options: #(…) >>>> >>>> New syntax: >>>> >>>> self nbCallout stdcall; >>>> options: #(…); >>>> function: #(…) module: … >>>> >>>> ---- >>>> >>>> New API and syntax: >>>> >>>> self nbCallout function: <signature> address: [ address block ] >>>> >>>> generate code for calling a function located at given address with >>>> given signature. >>>> The address of function is provided by user in address block, which >>>> should return a pointer to the function (NBExternalAddress or Unsigned >>>> integer value, representing an absolute address of function). >>>> This API is useful, when you need to call some function which is not >>>> exported by via DLL symbol directly, but indirectly. >>>> >>>> The old NBFFICallout API is still there, but use of it is strongly >>>> discouraged. And it will be removed eventually. So be warned! :) >>>> >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko. >>>> >>> >> >> >> >> -- >> Dr. Ciprian TEODOROV >> Ingénieur Développement CAO >> >> tél : 06 08 54 73 48 >> mail : [email protected] >> www.teodorov.ro > > > > -- > Best regards, > Igor Stasenko. >
