- Pharo-dev - lists.pharo.org

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

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

by Alain Rastoul

On 26/02/2016 10:16, stepharo wrote: > Alain > > can you give two example how to use the contract: ? > > I would understand: > > <precondition: [can we pass a block here] > > > Stef > > Hi Stef, Yes this is completely inspired by Bertrand Meyer/Eiffel work. I did an help page on that in the package info description on smalltalkhub with more info, but here is an abstract: precondition, postconditions, invariants are smalltalk checking methods that returns true or false and check that the object will perform/has performed (pre/post) as expected and is in a coherent state (invariants) . This is not about program proof but run time checking. I first tried with a block expressed as text in pragma as you suggest (and as done in some frameworks with comments) but it was difficult to use MetaLink with that, and MetaLink is a powerfull tool I wouldn't (and probably couldn't!) rewrite Adding smalltalk methods is much more powerfull than simple text since it integrates well with standard tools (debugger, browsers etc). Those checks can be compiled in all the methods with the Icecompiler and removed by recompiling the class with the standard compiler. examples : an invariant (a condition that is *allways* true) on a MyCollection class would be expressed as a checkIndex method of class MyCollection like: checkIndex <contract: invariant> ^ firstIndex > 0 meaning : on every method call to MyCollection, firstIndex *must* be > 0 if firstIndex goes <= 0 then the collection has a broken state this will be checked before and after *every call* of *every method* of MyCollection (except in the constructor an in other contract methods). a pre condition to a call to add: method preAdd: anObject <contract: #required appliedTo: #( #add: )> ^ anObject ~= self meaning : you must not add a collection to itself (note: this is just an example and I am not sure of that, I think it does not make sense to add a collection to itself but may be this is allowed?) this will be checked before every call to MyCollection>>add: (note2: appliedTo: allows to apply this check to several specific methods - I didn't tested it yet but if it does not work then this is a bug) a post condition that would be checked after every call: postAdd: anObject <contract: #ensured appliedTo: #( #add: )> ^ self includes: anObject . woudl check that after adding an object to a Mycollection, the collection effectivly includes the object. If it does not, this is reported as an error. names (checkIndex, preAdd: , postAdd:) are not important, they are like other methods of MyCollection. The important thing is the 'appliedTo' part of the pragma who indicates to which methods the contract applies.

Feb. 26, 2016

Re: [Pharo-dev] Got some DNU using Spotter but I could not repeat it

by Marcus Denker

> On 26 Feb 2016, at 10:30, stepharo <stepharo(a)free.fr> wrote: > > >> Hi, >> >> Was it not the SubscriptOutOfBounds error? > > Yes I think. > >> This is because of Rubric, but it should not appear anymore in the latest Pharo with the fix of Marcus. > I still can happen with methods / code styled > 1000 characters. I just enabled the non-forking code path again. (which makes looking at methods much nicer, too. Feels much faster due to no refreshing twice). But for large methods, the old problem exists. Another problem that might be fixed or not (in progress) is the TT-font related errorâ¦ Marcus

Feb. 26, 2016

Re: [Pharo-dev] Could we move back Bloc jenkins job under Pharo contribution?

by stepharo

Ok you should tell us and we will see what we can do. In fact I thought the job was not refreshing but this just the launcher that does not refresh. Le 26/2/16 10:35, Aliaksei Syrel a Ã©crit : > pharo-contribution is unstable. build fails randomly with java's > NullPointerExeption. Cairo is not installed on all machines. slaves > get stuck. it is a pain. I just want normal build. Doru said it is ok > for him to have bloc build for me for a moment. if you want I can copy > config to pharo-contrib > > Cheers, > Alex > > On Fri, Feb 26, 2016 at 10:21 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi > > Could we move back Bloc jenkins job under Pharo contribution? > Because this is strange to have it under Moose and I would like > students to be able to find it > easily. Apparently the build is strange because it does not load > the latest > version. I will try to sit with christophe and see the setup. > > Stef > > >

Feb. 26, 2016

Re: [Pharo-dev] Could we move back Bloc jenkins job under Pharo contribution?

by Aliaksei Syrel

pharo-contribution is unstable. build fails randomly with java's NullPointerExeption. Cairo is not installed on all machines. slaves get stuck. it is a pain. I just want normal build. Doru said it is ok for him to have bloc build for me for a moment. if you want I can copy config to pharo-contrib Cheers, Alex On Fri, Feb 26, 2016 at 10:21 AM, stepharo <stepharo(a)free.fr> wrote: > Hi > > Could we move back Bloc jenkins job under Pharo contribution? > Because this is strange to have it under Moose and I would like students > to be able to find it > easily. Apparently the build is strange because it does not load the latest > version. I will try to sit with christophe and see the setup. > > Stef > > >

Feb. 26, 2016