- Pharo-dev - lists.pharo.org

Re: [Pharo-project] What the best way to implement week dictionary cache

by Denis Kudriashov

> > You could take a look at the WeakDictionary that ships in a standard > Squeak image, if there isn't already one lying around in Pharo. There > are several classes using weak references. > I will look at squeak stuff. But my question more about about conceptual problem: I need week dictionary which values has reference to it key. Can it be really week? I think it can be kind of "ephemeron problem" and such dictionary contents will never be garbaged. Is ephemerons supported by latest vm? In pharo I see two classes: WeakKeyDictionary and WeakValueDictionary. What you think I should use to implement my requirements: cache which can be cleaned by garbage collector due to weak keys or values? 2012/11/27 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Ghost I think it is just implementation of very skin proxy objects? Is it related to weak dictionary cache?

Nov. 27, 2012

[Pharo-project] Changes in announcements

by Ezequiel Lamonica

Hi, I was reviewing with Esteban about the lack of some announcements in the system and some bugs in other ones. I've been working on that for this week. This is the list: -MethodRename -Snapshot -Session (i don't know if this is necessary) -VariableAdded (one for every kind) -VariableRemoved (one for every kind) -Protocols (add/modif/remove/rename) -TraitComposition - When a package is created, the announcement is not released This only happens when a class is created with that category. -When I modify a class and also I change its category, then only class recategorized announcement is sent -Package removed is not sent

Nov. 27, 2012

Re: [Pharo-project] What the best way to implement week dictionary cache

by StÃ©phane Ducasse

did you look at Ghost? Because mariano worked during one year on it. Stef On Nov 27, 2012, at 8:56 AM, Denis Kudriashov wrote: > Hello. > > I want implement cache for proxy objects. > I need some kind of dictionary which I can request for proxy of actual object. And any user of actual objects will work with same instances of proxies. And every proxy object has reference to actual object. > > Obvious solution is basic dictionary with actual objects as keys and proxy-objects as values. > But next I want my dictionary be week. And when nobody uses actual object it should be garbaged and my cache of proxies should be cleaned from unused proxies/actuals. > > Is it possible to implement such cache? And how it can be done? > > Best regards, > Denis

Nov. 27, 2012

Re: [Pharo-project] Got our first pharo consortium contract :)

by StÃ©phane Ducasse

Norbert >> Great!. And being the first is always something special :) Do you think the fees can be transferred already this year? We decided to do a pro-rata so that people do not think that we are trying to steal them and also to make sure that everybody can join at any time without thinking too much. So it would mean 1 month so it will be probably for january. Now if you want to pay the full price we can do it :). Stef

Nov. 27, 2012

Re: [Pharo-project] Got our first pharo consortium contract :)

by StÃ©phane Ducasse

I will ask. On Nov 27, 2012, at 9:56 AM, Norbert Hartl wrote: > > Am 26.11.2012 um 22:01 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> Hi guys >> >> This is a great day. We got our first pharo consortium contract signed by a great >> company: 2Denker :) >> > Great!. And being the first is always something special :) Do you think the fees can be transferred already this year? > > Norbert > >> Thanks for your trust! >> >> Soon the web site will get from the ground. >> Esteban got distracted by some VM bug chasing parties but he will be back on it. >> >> Stef > >

Nov. 27, 2012

Re: [Pharo-project] Got our first pharo consortium contract :)

by Norbert Hartl

Am 26.11.2012 um 22:01 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi guys > > This is a great day. We got our first pharo consortium contract signed by a great > company: 2Denker :) > Great!. And being the first is always something special :) Do you think the fees can be transferred already this year? Norbert > Thanks for your trust! > > Soon the web site will get from the ground. > Esteban got distracted by some VM bug chasing parties but he will be back on it. > > Stef

Nov. 27, 2012

Re: [Pharo-project] Internship

by StÃ©phane Ducasse

On Nov 26, 2012, at 10:02 AM, Goubier Thierry wrote: > Le 23/11/2012 19:04, StÃ©phane Ducasse a Ã©crit : >> thierry >> >> we will publish this offer. >> Now did you look at dave mason work on C header parsing. > > Hi Stef, > > no I haven't but I can have a look if you had any pointer. > > I started doing C parsing out of Lex/Yacc and studying C implementations (pcc, gcc before 4.0, gcc 4+, CLANG/LLVM) and ocaml (CIL, Frama-C) (looked a bit at ANTLR as well). After a few years of C/Flex/Bison, I moved to Pharo/SMACC. this is cool. what is the license of the Pharo one? > > One of my C-based parser has been modified for use in the toolchain of Kalray (http://www.kalray.eu/products/mppa-accesscore/) > > Thierry > >> Stef >> >> On Nov 22, 2012, at 3:42 PM, Goubier Thierry wrote: >> >>> Hi all, >>> >>> I'm looking for some help in parsing C files (and the opportunity to use Petit Parser (Parseur?)) so I'm looking for an internship candidate (Master level). >>> >>> The objective is to do a C preprocessor with a targeted integration in an existing C parser, and, in particular, provide high-level information about applied macros/defines for the tokens provided to the C parser itself. Platform should be Pharo (2.0:)). >>> >>> Place is Saclay, SW of Paris. The lab has a strong team on compilation tool chains for embedded manycores, from programming language design down to micro-kernel and mapping, and is able to select good interns for further work opportunities. >>> >>> http://www.cea.fr/ressources-humaines/stages-et-formation-en-alternance/les… >>> >>> Regards, >>> >>> Thierry >>> -- >>> Thierry Goubier >>> CEA list >>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>> 91191 Gif sur Yvette Cedex >>> France >>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>> >> >> >> > > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Nov. 27, 2012

Re: [Pharo-project] What the best way to implement week dictionary cache

by Frank Shearar

On 27 November 2012 07:56, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hello. > > I want implement cache for proxy objects. > I need some kind of dictionary which I can request for proxy of actual > object. And any user of actual objects will work with same instances of > proxies. And every proxy object has reference to actual object. > > Obvious solution is basic dictionary with actual objects as keys and > proxy-objects as values. > But next I want my dictionary be week. And when nobody uses actual object it > should be garbaged and my cache of proxies should be cleaned from unused > proxies/actuals. > > Is it possible to implement such cache? And how it can be done? You could take a look at the WeakDictionary that ships in a standard Squeak image, if there isn't already one lying around in Pharo. There are several classes using weak references. frank > Best regards, > Denis

Nov. 27, 2012

[Pharo-project] What the best way to implement week dictionary cache

by Denis Kudriashov

Hello. I want implement cache for proxy objects. I need some kind of dictionary which I can request for proxy of actual object. And any user of actual objects will work with same instances of proxies. And every proxy object has reference to actual object. Obvious solution is basic dictionary with actual objects as keys and proxy-objects as values. But next I want my dictionary be week. And when nobody uses actual object it should be garbaged and my cache of proxies should be cleaned from unused proxies/actuals. Is it possible to implement such cache? And how it can be done? Best regards, Denis

Nov. 27, 2012

Re: [Pharo-project] [ANN] NativeBoost v 1.7

by Igor Stasenko

On 26 November 2012 22:07, Camillo Bruni <camillobruni(a)gmail.com> wrote: > time to move to smalltalkhub... > no.. this is an in-image issue.. i suspecting something broke version info serialization. the .mcz files are no corrupt, but parser cannot parse the version information.. for some reason. the strings there are storeed in strange format.. looks like i mistakenly typed non-ascii character in commit log, and it serialized the unicode string.. but cannot read it back > On 2012-11-26, at 18:01, Igor Stasenko <siguctua(a)gmail.com> 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 <ciprian.teodorov(a)gmail.com> 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 <guygantuan(a)gmail.com> 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 <siguctua(a)gmail.com> >>>> 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 : ciprian.teodorov(a)gmail.com >>> www.teodorov.ro >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- Best regards, Igor Stasenko.

Nov. 27, 2012