November 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Tuning Opal Optimizations

by Sven Van Caekenberghe

On 21 Nov 2013, at 12:30, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > This mechanism does not work with Monticello. > > On my builds I have for this case something similar to: > > > ./pharo $JOB_NAME.image config $REPO ConfigurationOfMyProject --install=bleedingEdge > ./pharo $JOB_NAME.image eval --save 'SmalltalkImage compilerClass: OpalCompiler. Compiler recompileAll.â Thanks, ClÃ©ment, that works. I now do a ./pharo $JOB_NAME.image eval --save 'PEGParser recompile.â so that OPAL picks up the options. > 2013/11/21 Sven Van Caekenberghe <sven(a)stfx.eu> > > On 19 Nov 2013, at 16:45, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> > >> Yes, you can do it per class-hierarchyâ¦ you can implement on the class side a method to parametrize the compiler: > >> > >> compiler > >> ^super compiler options: #(- optionInlineTimesRepeat) > > > > Thanks, Marcus, that works just great. > > Marcus, > > Are we sure this option mechanism works when loading code through Monticello ? > > I mean, this build fails the PEGParser tests: > > https://ci.inria.fr/pharo-contribution/job/Xtreams/ > > but it includes the #compiler options in Xtreams-Parsing-nice.7 > > Could it not be that this is a chicken-egg problem: the #compiler options are only there _after_ the class is loaded/compiled, or maybe it is an instance/class side problem ? > > Sven > > >

Nov. 21, 2013

Re: [Pharo-dev] NativeBoost: Documentation Suggestion and Question

by Sean P. DeNigris

> mm.. well, i prefer that fairly common would be to pass meaningful data back and forth rather than > dummy values. I don't understand... when I say "fairly common", I mean that in the C world, it seems common to use null-passing for optional arguments. I'm not saying that it's a good idea, but we don't have control over that, so... > For that best solution, IMO, would be to use 2 methods which call same function, > but one uses 'nil' in function signature (and therefore method doesn't takes extra argument), > while other takes extra argument but doesn't accepts nils, for sure. Yuck ;) ----- Cheers, Sean -- View this message in context: http://forum.world.st/NativeBoost-Documentation-Suggestion-and-Question-tp4… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 21, 2013

Re: [Pharo-dev] Old ClassBuilder remove!

by Sven Van Caekenberghe

On 21 Nov 2013, at 13:21, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Triple impressive! This is another sample of an apparently tiny change that actually has deep impact on the future of our beloved environment. > > Ladies and gentlemen, I know you are busy, but please take the time to acknowledge it :) > > Doru +10 Also, all these changes in different areas reinforce each other. That is Pharo. > > On Thu, Nov 21, 2013 at 12:58 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > wow, impressive! > > > On Thu, Nov 21, 2013 at 9:02 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Yesterday Camille did the change to finally remove the old class builder! > (just a removal + a small change to NativeBoost to use the new class builder to create anonymous classes). > > This means > - 1000 Loc of completely un-understandable code removed. > - we now 100% run on the new class builder from the Slot Project. > > Next on the list (not all for Pharo3): > > - remove PackageInfo > - old Browser + CodeHolder hierarchy > - PseudoClass&Co â> Ring > - old AST+Compiler (this in Pharo4) > > We already did (all in Pharo3): > -> remove URI > -> deprecated Url for ZnUrl > -> removed HTTPSocket facade > -> MIMEType retired for ZnMimeType > -> old Debugger is removed > -> Class categories are replaced by Protocols > > I am quite sure that these cleanups will enable us to build a lot of very interesting things > in the future. > > Marcus > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Nov. 21, 2013

Re: [Pharo-dev] How to encrypt a password?

by Mariano Martinez Peck

Hi Paul, and just to be sure I understand...none of them could work as a two-way encryption, right? The only one is your Pharo's version of Blowfish but that only works with 8 chars long. Is it like this? Or is there any other two-way encryption? Thanks! On Thu, Nov 21, 2013 at 1:35 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Davide Varvello wrote > > Hi Paul, > > I resume this old thread because it's not clear to me which package > > download to make BCryptLinuxFFI work > > > > In an other thread you point to: > > MCHttpRepository > > location: 'http://smalltalkhub.com/mc/Cryptography/Blowfish/main > ' > > user: '' > > password: '' > > > > but there is no BCryptLinuxFFI there. > > Can you help me please? > > > > Cheers > > Davide > > > Hi Davide, > > > You need to be on Linux and > > On pharo or squeak > - have a 32bit version of libxcrypt installed. > - use this mcz > > > http://www.squeaksource.com/Cryptography/PasswordHashingFFI-PaulDeBruicker.… > or > > > http://www.smalltalkhub.com/mc/Cryptography/Cryptography/main/PasswordHashi… > (they're the same file) > > On GemStone > - have a 64bit version of libxcrypt installed > - use this mcz > > http://seaside.gemtalksystems.com/ss/Cryptography/PasswordHashingFFI-PaulDe… > > > The Blowfish stuff is an implementation of the cipher > (https://en.wikipedia.org/wiki/Blowfish_%28cipher%29) BCrypt uses > blowfish > as its encryption mechanisim, calling it tens to hundreds of thousands of > times. > > > The PasswordHashingFFI package also includes support for accessing the > crypt(3) library so you can use SHA512 password hashing too if you like (or > other mechanisms it supports like DES, MD5, etc) > > > Hope this helps > > Paul > > > > -- > View this message in context: > http://forum.world.st/How-to-encrypt-a-password-tp3933585p4724035.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

Nov. 21, 2013

[launcher] Re: PharoLauncher

by btc＠openinworld.com

Well spotted. It is explained by PharoLauncher>>setImageRepository: aTemplateRepository templateRepository: anImageRepository also being wrong and reversed. If you might like to contribute to PharoLauncher and want to get into the swing of things, pharo.fogbugz.com has a 'Launcher' project'where you can log Cases to which you can attach mcz files. btw, you might find the various #settingsOn: methods interesting. btw2, for a while I had been collaborating with Damien in private, but we recently decided to move this to [pharo-users] and adding a [launcher] tag. I've cross-posted there. cheers -ben Mark Bestley wrote: > On 21/11/2013 15:00, Sean P. DeNigris wrote: >> Just starting to play with it... looks cool. >> >> One thing is that I'd like to be able to choose the default image >> location. >> It feels wrong to install them under ~/Library/Preferences on the Mac... >> > > Agreed > > > However I am confused by the code > > createLauncher > ^ self basicNew > setImageRepository: PhLTemplateGroupRepository > forSelectedGroups > templateRepository: PhLDirectoryBasedImageRepository > inPharoPreferencesDirectory; > initialize; > yourself > > Aren't the parameters of setImage and template the wrong way round? ie > it seems to pass the template dir to the image and vice versa >

Nov. 21, 2013

Re: [Pharo-dev] NativeBoost: Documentation Suggestion and Question

by Igor Stasenko

On 21 November 2013 17:34, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Igor Stasenko wrote > > a simplest way is to pass dumb and stupid > > NBExternalAddress null. > > Yes! That worked :) Thank you!! > > > Igor Stasenko wrote > > except i think nil -> void * is not accepted by default. > > Why is that disabled by default? It seems like a fairly common operation... > > > mm.. well, i prefer that fairly common would be to pass meaningful data back and forth rather than dummy values. For that best solution, IMO, would be to use 2 methods which call same function, but one uses 'nil' in function signature (and therefore method doesn't takes extra argument), while other takes extra argument but doesn't accepts nils, for sure. > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/NativeBoost-Documentation-Suggestion-and-Question-tp4… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- Best regards, Igor Stasenko.

Nov. 21, 2013

Re: [Pharo-dev] Smalltalks 2013 video now available

by Craig Latta

> Thanks Andres! This is sooooo important to share the conferences > beyond the slice of our community attending :) Hear hear! Thanks, Andres! -C -- Craig Latta www.netjam.org/resume +1 510 984 8117 (Skype rings this until 31 January 2014)

Nov. 21, 2013

Re: [Pharo-dev] NativeBoost: Documentation Suggestion and Question

by Sean P. DeNigris

StÃ©phane Ducasse wrote > could you propose something for it: adding a class ReadMe? DocuMe? > Adding it to the help? I'll organize my observations. A few that stood out: - In signature - you must type "ulong", not "unsigned long" - when passing objects as arguments, don't need "*" unless you might pass null - typedefs: declare in shared pool - Pass a pointer receiving external object as an argument: NBExternalAddress new - Pass nil as a pointer argument: NBExternalAddress null ----- Cheers, Sean -- View this message in context: http://forum.world.st/NativeBoost-Documentation-Suggestion-and-Question-tp4… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 21, 2013

Re: [Pharo-dev] How to encrypt a password?

by Paul DeBruicker

Davide Varvello wrote > Hi Paul, > I resume this old thread because it's not clear to me which package > download to make BCryptLinuxFFI work > > In an other thread you point to: > MCHttpRepository > location: 'http://smalltalkhub.com/mc/Cryptography/Blowfish/main' > user: '' > password: '' > > but there is no BCryptLinuxFFI there. > Can you help me please? > > Cheers > Davide Hi Davide, You need to be on Linux and On pharo or squeak - have a 32bit version of libxcrypt installed. - use this mcz http://www.squeaksource.com/Cryptography/PasswordHashingFFI-PaulDeBruicker.… or http://www.smalltalkhub.com/mc/Cryptography/Cryptography/main/PasswordHashi… (they're the same file) On GemStone - have a 64bit version of libxcrypt installed - use this mcz http://seaside.gemtalksystems.com/ss/Cryptography/PasswordHashingFFI-PaulDe… The Blowfish stuff is an implementation of the cipher (https://en.wikipedia.org/wiki/Blowfish_%28cipher%29) BCrypt uses blowfish as its encryption mechanisim, calling it tens to hundreds of thousands of times. The PasswordHashingFFI package also includes support for accessing the crypt(3) library so you can use SHA512 password hashing too if you like (or other mechanisms it supports like DES, MD5, etc) Hope this helps Paul -- View this message in context: http://forum.world.st/How-to-encrypt-a-password-tp3933585p4724035.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 21, 2013

Re: [Pharo-dev] NativeBoost: Documentation Suggestion and Question

by Sean P. DeNigris

Igor Stasenko wrote > a simplest way is to pass dumb and stupid > NBExternalAddress null. Yes! That worked :) Thank you!! Igor Stasenko wrote > except i think nil -> void * is not accepted by default. Why is that disabled by default? It seems like a fairly common operation... ----- Cheers, Sean -- View this message in context: http://forum.world.st/NativeBoost-Documentation-Suggestion-and-Question-tp4… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 21, 2013