February 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Who is using Pharo Launcher and for what

by Alain Rastoul

On 20/02/2016 11:49, Damien Cassou wrote: > For my CV, I need to know who is using the stuff I'm doing. If you use > the Pharo Launcher, could you please tell me in which context (e.g., > which company, open-source project) and what you use it for (e.g., > download from CI, standard Pharo)? > > I don't need long paragraphs, just give me the keywords please. > > Thanks > I use PharoLauncher whenever I launch Pharo for personal developments, mainly on linux and sometimes on windows. I download from CI. it really helps dealing with several Pharo images, an invaluable tool. -- Alain

Feb. 26, 2016

Re: [Pharo-dev] Run time checking with design by contract assertions

by Alexandre Bergel

I still do not understand. I would imagine something like: foo <precondition: #invariant> <postcondition: #invariant> self bar But, all in all, what are we using pragmas here? I can always do: self assert: [ â¦ ] description: â¦ Maybe we should specific a method called contractInvariant that is always executed before and after. Using Reflectivity. Alexandre > On Feb 26, 2016, at 11:50 AM, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: > > On 26/02/2016 11:26, Alexandre Bergel wrote: >> Hi Alain, >> >> Having contract is a valuable effort! >> >>> On Feb 26, 2016, at 11:12 AM, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: >>> >>> <contract: #ensured appliedTo: #( #add: )> >> >> What does that mean? >> <contract: #ensured appliedTo: #( #add: )> >> >> Alexandre >> > Hi Alexandre, > > a method with a pragma > <contract: #ensured appliedTo: #( #add: ) > > means it is a check that must be ensured by (enforced by) the method to which it applies (here add:). > The add: method of the object *must* verify this check, when the check is executed, it must return true. > > May be the terms I've choosed are confusing at first, but it was voluntary, preCondition, postCondition are too much program execution oriented IMHO, not enough assertive . > > btw it is easy to change: > one could say here: > <contract: postcondition on: #( #add: )> > > may be better ? > > or may be better to support both ... :) > > > Alain > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 26, 2016

Re: [Pharo-dev] Run time checking with design by contract assertions

by Alain Rastoul

On 26/02/2016 11:26, Alexandre Bergel wrote: > Hi Alain, > > Having contract is a valuable effort! > >> On Feb 26, 2016, at 11:12 AM, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: >> >> <contract: #ensured appliedTo: #( #add: )> > > What does that mean? > <contract: #ensured appliedTo: #( #add: )> > > Alexandre > In fact I think may be better to use #before and #after since it is what is used internally with MetaLink, it is clear and more developper friendly, with singular and plural forms : for contracts applied to only one method: <contract: #before method: #add:> <contract: #after method: #add:> for contracts applied to several methods: <contract: #before methods: #( #add: #addLast: #addIfNotPresent:)> <contract: #after methods: #( #add: #addLast: #addIfNotPresent:)> what do you think of that ? -- Alain

Feb. 26, 2016

Re: [Pharo-dev] Run time checking with design by contract assertions

by Alain Rastoul

On 26/02/2016 11:50, Alain Rastoul wrote: > one could say here: > <contract: postcondition on: #( #add: )> Correction, after Nicolai's observation: > <contract: #postcondition on: #( #add: )> (symbol) -- Alain

Feb. 26, 2016

Re: [Pharo-dev] Run time checking with design by contract assertions

by Alain Rastoul

On 26/02/2016 11:26, Alexandre Bergel wrote: > Hi Alain, > > Having contract is a valuable effort! > >> On Feb 26, 2016, at 11:12 AM, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: >> >> <contract: #ensured appliedTo: #( #add: )> > > What does that mean? > <contract: #ensured appliedTo: #( #add: )> > > Alexandre > Hi Alexandre, a method with a pragma <contract: #ensured appliedTo: #( #add: ) > means it is a check that must be ensured by (enforced by) the method to which it applies (here add:). The add: method of the object *must* verify this check, when the check is executed, it must return true. May be the terms I've choosed are confusing at first, but it was voluntary, preCondition, postCondition are too much program execution oriented IMHO, not enough assertive . btw it is easy to change: one could say here: <contract: postcondition on: #( #add: )> may be better ? or may be better to support both ... :) Alain

Feb. 26, 2016

Re: [Pharo-dev] "error: 'math.h' file not found" when building the new VM

by Esteban Lorenzano

read the instructions :) https://github.com/pharo-project/pharo-vm/blob/spur64/README-Win32.md <https://github.com/pharo-project/pharo-vm/blob/spur64/README-Win32.md> > On 26 Feb 2016, at 11:24, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Hi! > > I am trying to build the VM, according to the instruction given on https://github.com/pharo-project/pharo-vm > However, I get an error: > > eloper/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk' > /Users/alexandrebergel/Desktop/VM_TMP/pharo-vm/src/plugins/JPEGReaderPlugin/JPEGReaderPlugin.c:10:10: fatal error: 'math.h' file not found > #include <math.h> > > Where this math.h is supposed to be? > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Feb. 26, 2016

Re: [Pharo-dev] Run time checking with design by contract assertions

by Alain Rastoul

On 26/02/2016 11:23, Nicolai Hess wrote: > can you use symbols only for pragma arguments, please. > > <contract: #invariant> > instead of > <contract: invariant> > > I am about to change rbparser to only allow constant literal arguments > > Yes, no problem I noticed it worked but was not sure it was right thank you for pointing that

Feb. 26, 2016

Re: [Pharo-dev] Run time checking with design by contract assertions

by Alexandre Bergel

Hi Alain, Having contract is a valuable effort! > On Feb 26, 2016, at 11:12 AM, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: > > <contract: #ensured appliedTo: #( #add: )> What does that mean? <contract: #ensured appliedTo: #( #add: )> Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 26, 2016

"error: 'math.h' file not found" when building the new VM

by Alexandre Bergel

Hi! I am trying to build the VM, according to the instruction given on https://github.com/pharo-project/pharo-vm However, I get an error: eloper/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk' /Users/alexandrebergel/Desktop/VM_TMP/pharo-vm/src/plugins/JPEGReaderPlugin/JPEGReaderPlugin.c:10:10: fatal error: 'math.h' file not found #include <math.h> Where this math.h is supposed to be? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 26, 2016

Re: [Pharo-dev] Run time checking with design by contract assertions

by Nicolai Hess

2016-02-25 23:48 GMT+01:00 Alain Rastoul <alf.mmm.cat(a)gmail.com>: > Hi, > > I have downloaded a first version of IceCompiler, a small tool who allow > run time checks embedding in pharo classes on Smalltalkhub at > > http://smalltalkhub.com/#!/~AlainRastoul/IceCompiler > > If some interested pharoers are willing to give me feedback on this > package I would greatly appreciate. > This is not an announce but a request for feedback to advanced pharo users > , since it is an alpha version with probably killing side effects. > There is no ConfigurationOf as of today(there will be), but there is no > dependency and the package loads well in a fresh standard Pharo 5.0. > > > Checks are written in standard smalltalk methods with design-by-contract > style pragmas like > > <contract: invariant> > <contract: #ensured appliedTo: #( #add: )> > <contract: #required appliedTo: #( #add: )> > can you use symbols only for pragma arguments, please. <contract: #invariant> instead of <contract: invariant> I am about to change rbparser to only allow constant literal arguments > > Contract method calls are compiled in specified classes (with subclasses) > in order to make bullet-proofing run test phases of Pharo code/image > and to help in hard bug cases. > > > Before trying this package, please read the comments on smalltalk hub > page, because if misused it may break your image, and do not use on > standard important classes (Array, String, Dictionary, Collection etc.) ... > unless you like danger :) > > > Many thanks in advance > > > regards, > > Alain > > >

Feb. 26, 2016