- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] How to get launcher launching Spur images?

by Stephan Eggermont

On 13-01-16 17:09, Serge Stinckwich wrote: > Great ! Works for me now with the last version on mac os x. > > Maybe new binary version for windows and mac should be provide here for newbies: > https://ci.inria.fr/pharo/view/Launcher/ I've committed a new configuration, promoting this to #stable and using the latest versions of dependencies. It is not yet really friendly enough for newbies, but that's a next step Stephan

Jan. 13, 2016

Re: [Pharo-dev] Bad layoutFrame>>#hash

by David Allouche

> On 12 Jan 2016, at 20:59, stepharo <stepharo(a)free.fr> wrote: > > Hi david > > I rad the wikipedia page you mention and this looks a bit obvious to me. I knew this. > now it does not really help fixing the problem you mention. > > Stef Since you asked for itâ¦ The #hash method is used in Pharo to separate objects in bucket-based data structures. It must have one required property which is required data integrity: A. Objects that are equal according to #= must have equal hashes. It should have two desirable properties that are required to support the algorithmic assumptions of bucket-based data structures: B. Objects that are not equal should have different hashes. Ideally, the probability of hash collision should by 1/N where N is the size of hash value space. C. The hash values should spread as much as possible over their value space. For example: ProtoObject>>#identityHash. How these two desirable properties can be implemented depend on the actual distribution of the value used to compute the hash. An object can safely use XOR hashing if its instance variables are all different objects that already provide a hash method with these two properties. For example, an object whose behaviour is defined by several of singleton delegates of different classes that do not override Object>>#hash. But if the instance variables are not guaranteed to have those properties, it is necessary to more thoroughly "mix the bits". For example: SequenceableCollection>>#hash. hash | hash | hash := self species hash. 1 to: self size do: [:i | hash := (hash + (self at: i) hash) hashMultiply]. ^hash The mixing of the bits is done by the combination of addition and hashMultiply. The value of "species hash" does not need to be processed by hashMultiply, because it is probably computed by ProtoObject>>identityHash, and that already provides C. LayoutFrame is a particularly good example of a data structure that should not use XOR hashing. Its instance variables provide none of the required properties: SmallInteger>>#hash is just ^self. In addition, common LayoutFrame instances tend to use pairs of identical values in their instance variables. Like 0@0 corner: 1@1, or Margin fromNumber: 10. A good hash function for LayoutFrame needs to: Get hashes for each instance variable that provides A and B. Combine them in a way that is order-sensitive (to maintain B) and that does some extra mixing (to provide C). Now, we can assume that common values for the instance variables will be instances of SmallInteger, Float, or Fraction. By the way, you can see in Fraction>>#hash, that a comment mentions the assumption that the fraction is already reduced, that is what makes it acceptable to use bitXor. The hash of SmallInteger does provide A and B, but not C. The hash of Float is harder to understand, but tests show that it provide distinct values for 0.5, 0.25 and 0.125. So it hopefully provides B for the range of values of interest to LayoutFrame. Another class that has similar hashing constraints to LayoutFrame is Point. Its hash method is: hash "Hash is reimplemented because = is implemented." ^(x hash hashMultiply + y hash) hashMultiply It does not include species in the computation, which is less than ideal because it favours collisions with objects of different species that have a similar content and a the same #hash algorithm. Finally, it is probably not necessary or useful to use the accessors to get to the instance variables. So a good implementation would be this (untested, there might be a typo or two) hash | hash | hash := self species hash hash := (hash + leftFraction hash) hashMultiply hash := (hash + leftOffset hash) hashMultiply hash := (hash + topFraction hash) hashMultiply hash := (hash + topOffset hash) hashMultiply hash := (hash + rightFraction hash) hashMultiply hash := (hash + rightOffset hash) hashMultiply hash := (hash + bottomFraction hash) hashMultiply hash := (hash + bottomOffset hash) hashMultiply ^ hash I am sure you could have figured that by yourself, by thinking about how hash values are used and by looking at the code of kernel classes, instead of getting offended and turning all defensive. I hope we can both learn from this episode. I do not enjoy antagonising people, but I will not write lengthy messages like this one every time someone questions my thinking. Have a nice day. > Le 11/1/16 10:09, David Allouche a Ã©crit : >> Since it's not obvious why xor-ing is a bad way to produce hash, here is a link that gives some background >> >> https://en.wikipedia.org/wiki/Hash_function#Uniformity >> >>> On 11 Jan 2016, at 10:01, David Allouche <david(a)allouche.net> wrote: >>> >>> I happened to look at the new code for LayoutFrame>>#hash >>> >>> hash >>> ^self species hash bitXor: >>> (self leftFraction bitXor: >>> (self leftOffset bitXor: >>> (self topFraction bitXor: >>> (self topOffset bitXor: >>> (self rightFraction bitXor: >>> (self rightOffset bitXor: >>> (self bottomFraction bitXor: >>> self bottomOffset))))))) >>> >>> This is a terrible, terrible way to compute a hash. >>> >>> 0 xor 0 = 1 xor 1 = 2 xor 2 = etc. >>> >>> NEVER compute hashes with xor, that's wrong, and it causes horrible, hard to debug, performance bugs down the road. >>> >>> SequenceableCollection>>#hash looks more like a correct way of doing it. I do not know what is the correct, efficient way to reuse this logic in LayoutFrame>>#hash. >>> >>> By the way, how do you guys do code reviews for code integrated into the core? >>> >> >> > >

Jan. 13, 2016

Re: [Pharo-dev] How to get launcher launching Spur images?

by Serge Stinckwich

Great ! Works for me now with the last version on mac os x. Maybe new binary version for windows and mac should be provide here for newbies: https://ci.inria.fr/pharo/view/Launcher/ Thank you guys. On Wed, Jan 13, 2016 at 4:46 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > >> -----Message d'origine----- >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de >> stepharo >> EnvoyÃ© : mercredi 13 janvier 2016 16:37 >> Ã : Pharo Development List >> Objet : Re: [Pharo-dev] How to get launcher launching Spur images? >> >> So what is the conclusion? >> Can anybody get the launcher open both prespur and spur images? > > I can. You can try the latest version. It should work. > > Vincent >> >> Stef >> >> >> Le 13/1/16 13:16, Blondeau Vincent a Ã©crit : >> > I confirm it works under W7 with Spur and not spur images. >> > Thanks ! >> > >> > I think https://github.com/pharo-project/pharo-launcher/issues/1 can be >> closed now? >> > >> > Vincent >> > >> >> -----Message d'origine----- >> >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part >> >> de Stephan Eggermont EnvoyÃ© : mercredi 13 janvier 2016 12:35 Ã : >> >> pharo-dev(a)lists.pharo.org Objet : Re: [Pharo-dev] How to get launcher >> >> launching Spur images? >> >> >> >> On 13-01-16 12:25, Blondeau Vincent wrote: >> >>> Under Windows, this cmd is working: >> >>> OSProcess command: $" asString, vmCommand , '" "' , imagePath, '"'. >> >>> Does it work under Mac (with real double quotes and not 2 single >> quotes)? >> >>> If no, we should do something that is platform dependent.. >> >> Yes, it works. Please confirm if version 87 works for you >> >> >> >> Stephan >> >> >> >> >> > >> > >> > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage >> exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret >> professionnel. Si vous recevez ce message par erreur, merci d'en avertir >> immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne >> pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra >> Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs >> efforts soient faits pour maintenir cette transmission exempte de tout virus, >> l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne >> saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. >> > >> > This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive this e-mail >> in error, please notify the sender immediately and destroy it. As its integrity >> cannot be secured on the Internet, the Worldline liability cannot be triggered >> for the message content. Although the sender endeavours to maintain a >> computer virus-free network, the sender does not warrant that this >> transmission is virus-free and will not be liable for any damages resulting >> from any virus transmitted. >> > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Jan. 13, 2016

Re: [Pharo-dev] 17348 Enhance shortcut learnability

by Cyril Ferlicot D.

Le 12/01/2016 21:03, Henrik Nergaard a Ã©crit : > Hi Stef, > > > > Something like this? (see attachment) > > > > Best regards, > > Henrik > > Hi, I think it would be cool to also have a setting to get it with an #inform: instead of a full Morph. I would like to get a reminder of the shortcuts but not in all my screen. A little popup at the bottom left is less invasive. So I think that we should be able to get both. What do you think ? -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Jan. 13, 2016

Re: [Pharo-dev] How to get launcher launching Spur images?

by Cyril Ferlicot D.

Le 13/01/2016 16:36, stepharo a Ã©crit : > So what is the conclusion? > Can anybody get the launcher open both prespur and spur images? > > Stef > > > Since more than one week I can on Windows and Linux :) -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Jan. 13, 2016

Sounds like Goodies

by Torsten Bergmann

The dolphin 7 open source repo includes some contributions from Udo including an implementation for Levenshtein distance [1]. It's a single method + test case and easy to port. The algorithm [2] is useful to find out how close two strings are (approximate string matching). There is also SoundEx [4] and SoundsLike [5] (Soundex, Double Metaphone and NYSIIS algorithms) for Pharo available. I just want to let anyone know - just in case someone works on a more "robust" autocompletion that is also typo aware. ;) Having custom templates [6] like in Eclipse would also be good to have in future Pharo code editor. More to add to the wishlist? Damn ... Santa already passed by... Have fun T. [1] https://github.com/dolphinsmalltalk/Contributions/tree/master/Udo%20Schneid… [2] https://en.wikipedia.org/wiki/Levenshtein_distance [3] https://github.com/dolphinsmalltalk/Contributions/tree/master/Udo%20Schneid… [4] http://smalltalkhub.com/#!/~riverdusty/SXSoundEx [5] http://www.smalltalkhub.com/#!/~UdoSchneider/SoundsLike [6] http://www.tutorialspoint.com/eclipse/eclipse_code_templates.htm

Jan. 13, 2016

Re: [Pharo-dev] How to get launcher launching Spur images?

by Blondeau Vincent

> -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de > stepharo > EnvoyÃ© : mercredi 13 janvier 2016 16:37 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] How to get launcher launching Spur images? > > So what is the conclusion? > Can anybody get the launcher open both prespur and spur images? I can. You can try the latest version. It should work. Vincent > > Stef > > > Le 13/1/16 13:16, Blondeau Vincent a Ã©crit : > > I confirm it works under W7 with Spur and not spur images. > > Thanks ! > > > > I think https://github.com/pharo-project/pharo-launcher/issues/1 can be > closed now? > > > > Vincent > > > >> -----Message d'origine----- > >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part > >> de Stephan Eggermont EnvoyÃ© : mercredi 13 janvier 2016 12:35 Ã : > >> pharo-dev(a)lists.pharo.org Objet : Re: [Pharo-dev] How to get launcher > >> launching Spur images? > >> > >> On 13-01-16 12:25, Blondeau Vincent wrote: > >>> Under Windows, this cmd is working: > >>> OSProcess command: $" asString, vmCommand , '" "' , imagePath, '"'. > >>> Does it work under Mac (with real double quotes and not 2 single > quotes)? > >>> If no, we should do something that is platform dependent.. > >> Yes, it works. Please confirm if version 87 works for you > >> > >> Stephan > >> > >> > > > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout virus, > l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne > saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this e-mail > in error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, the Worldline liability cannot be triggered > for the message content. Although the sender endeavours to maintain a > computer virus-free network, the sender does not warrant that this > transmission is virus-free and will not be liable for any damages resulting > from any virus transmitted. > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Jan. 13, 2016

Re: [Pharo-dev] How to get launcher launching Spur images?

by Serge Stinckwich

At the moment, I have 2 Pharo Launcher one for pre-Spur images and another one for Spur images ... On Wed, Jan 13, 2016 at 4:36 PM, stepharo <stepharo(a)free.fr> wrote: > So what is the conclusion? > Can anybody get the launcher open both prespur and spur images? > > Stef > > > Le 13/1/16 13:16, Blondeau Vincent a Ã©crit : > >> I confirm it works under W7 with Spur and not spur images. >> Thanks ! >> >> I think https://github.com/pharo-project/pharo-launcher/issues/1 can be >> closed now? >> >> Vincent >> >>> -----Message d'origine----- >>> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de >>> Stephan Eggermont >>> EnvoyÃ© : mercredi 13 janvier 2016 12:35 >>> Ã : pharo-dev(a)lists.pharo.org >>> Objet : Re: [Pharo-dev] How to get launcher launching Spur images? >>> >>> On 13-01-16 12:25, Blondeau Vincent wrote: >>>> >>>> Under Windows, this cmd is working: >>>> OSProcess command: $" asString, vmCommand , '" "' , imagePath, '"'. >>>> Does it work under Mac (with real double quotes and not 2 single >>>> quotes)? >>>> If no, we should do something that is platform dependent.. >>> >>> Yes, it works. Please confirm if version 87 works for you >>> >>> Stephan >>> >>> >> >> >> Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage >> exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret >> professionnel. Si vous recevez ce message par erreur, merci d'en avertir >> immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne >> pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra >> Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs >> efforts soient faits pour maintenir cette transmission exempte de tout >> virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa >> responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un >> virus transmis. >> >> This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive this >> e-mail in error, please notify the sender immediately and destroy it. As its >> integrity cannot be secured on the Internet, the Worldline liability cannot >> be triggered for the message content. Although the sender endeavours to >> maintain a computer virus-free network, the sender does not warrant that >> this transmission is virus-free and will not be liable for any damages >> resulting from any virus transmitted. > > > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Jan. 13, 2016

Re: [Pharo-dev] 17348 Enhance shortcut learnability

by stepharo

Sweet! I was thinking to put it below and smaller but this is cool. Stef Le 12/1/16 21:03, Henrik Nergaard a Ã©crit : > > Hi Stef, > > Something like this? (see attachment) > > Best regards, > > Henrik > > *From:*Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *On Behalf > Of *stepharo > *Sent:* Monday, January 11, 2016 4:52 PM > *To:* Pharo Development List <pharo-dev(a)lists.pharo.org> > *Subject:* Re: [Pharo-dev] 17348 Enhance shortcut learnability > > Henrik > > Thanks. What I would love to get is > > another little morph below the shortcut with the name of the menu > like that we can learn that the tools xxx is launched with > shortcut cmd X > > I think that we should have a preference that does not flush the > counters at startup > > Stef > > Le 11/1/16 12:14, Henrik Nergaard a Ã©crit : > > Somehow it integrated > > ______________ > > Name: SLICE-Issue-17348-Enhance-shortcut-learnability-tr.2 > > Author: tr > > Time: 8 January 2016, 4:18:55.135106 pm > > UUID: 0aa30f76-84f3-0449-acde-172e56ea3615 > > Ancestors: SLICE-Issue-17348-Enhance-shortcut-learnability-tr.1 > > Dependencies: Morphic-Base-tr.526 > > better version > > instead of: > > ____________ > > Name: SLICE-Issue-17348-Enhance-shortcut-learnability-HenrikNergaard.2 > > Author: HenrikNergaard > > Time: 8 January 2016, 11:01:18.490743 pm > > UUID: 2a6f1c3f-a0b3-524d-9095-02fb42ab8358 > > Ancestors: SLICE-Issue-17348-Enhance-shortcut-learnability-tr.1 > > Dependencies: Morphic-Base-HenrikNergaard.526 > > Refactor of initial code. > > I have updated and merged a new slice (in Image 50521) which > should fix it. The correct version that should be integrated is: > > Name: SLICE-Issue-17348-Enhance-shortcut-learnability-HenrikNergaard.5 > > Author: HenrikNergaard > > Time: 11 January 2016, 12:17:08.504781 am > > UUID: f0271c17-07a7-0d4e-a6eb-d2fef9b2853c > > Ancestors: > SLICE-Issue-17348-Enhance-shortcut-learnability-HenrikNergaard.4 > > Dependencies: Morphic-Base-HenrikNergaard.530 > > remove unused variable. > > Best regards, > > Henrik > > *From:*Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *On > Behalf Of *Marcus Denker > *Sent:* Monday, January 11, 2016 11:35 AM > *To:* Pharo Development List <pharo-dev(a)lists.pharo.org> > <mailto:pharo-dev@lists.pharo.org> > *Subject:* Re: [Pharo-dev] 17348 Enhance shortcut learnability > > Hello, > > I wil reopen the issue and put your comment there. > > Marcus > > On 11 Jan 2016, at 09:56, Nicolai Hess <nicolaihess(a)gmail.com > <mailto:nicolaihess@gmail.com>> wrote: > > Can please someone translate / change the text in the > > Shortcut reminder Morph settings.( that got integrated in 50521) > > see my comment on > https://pharo.fogbugz.com/f/cases/17348/Enhance-shortcut-learnability#BugEv… > > and I asked for resubmitting the changes with proper author > initials > > instead of "tr" and if he signed the license agreement. > > Anyone knows more about "tr" ? > > And I am not sure if the right version is integrated. > > nicolai >

Jan. 13, 2016

Re: [Pharo-dev] How to get launcher launching Spur images?

by stepharo

So what is the conclusion? Can anybody get the launcher open both prespur and spur images? Stef Le 13/1/16 13:16, Blondeau Vincent a Ã©crit : > I confirm it works under W7 with Spur and not spur images. > Thanks ! > > I think https://github.com/pharo-project/pharo-launcher/issues/1 can be closed now? > > Vincent > >> -----Message d'origine----- >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de >> Stephan Eggermont >> EnvoyÃ© : mercredi 13 janvier 2016 12:35 >> Ã : pharo-dev(a)lists.pharo.org >> Objet : Re: [Pharo-dev] How to get launcher launching Spur images? >> >> On 13-01-16 12:25, Blondeau Vincent wrote: >>> Under Windows, this cmd is working: >>> OSProcess command: $" asString, vmCommand , '" "' , imagePath, '"'. >>> Does it work under Mac (with real double quotes and not 2 single quotes)? >>> If no, we should do something that is platform dependent.. >> Yes, it works. Please confirm if version 87 works for you >> >> Stephan >> >> > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Jan. 13, 2016