- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #737: 4597-Adding-string-executable-examples
by ci-pharo-ci-jenkins2＠inria.fr Sept. 15, 2019

Sept. 15, 2019

There is a new Pharo build available! The status of the build #737 was: FAILURE. The Pull Request #4598 was integrated: "4597-Adding-string-executable-examples" Pull request url: https://github.com/pharo-project/pharo/pull/4598 Issue Url: https://github.com/pharo-project/pharo/issues/4597 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #736: 2404-Morph-Theme
by ci-pharo-ci-jenkins2＠inria.fr Sept. 15, 2019

Sept. 15, 2019

There is a new Pharo build available! The status of the build #736 was: FAILURE. The Pull Request #4600 was integrated: "2404-Morph-Theme" Pull request url: https://github.com/pharo-project/pharo/pull/4600 Issue Url: https://github.com/pharo-project/pharo/issues/2404 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Help on Iceberg
by Hilaire Sept. 15, 2019

Sept. 15, 2019

Hi, I have been experimenting the contributing process for fixes. But I am doing wrongly some steps. If I understand correctly after push a pull request (PR) I should do a checkout of Pharo8. This last process I did not do it. I tried yesterday but 1. Not clear from where in the UI and from which repo 2. I tried one guessed scenario and it was refused. Idea? See: https://github.com/pharo-project/pharo/pull/4580#issuecomment-531322034 Now I should probably start with a fresh P8, but I don't want to loose my previous fixes (I guess should be on my own repo) Hilaire -- Dr. Geo http://drgeo.eu

2 7

[Pharo 8.0] Build #735: 4537-Integrate-MiniBeacon
by ci-pharo-ci-jenkins2＠inria.fr Sept. 13, 2019

Sept. 13, 2019

There is a new Pharo build available! The status of the build #735 was: FAILURE. The Pull Request #4588 was integrated: "4537-Integrate-MiniBeacon" Pull request url: https://github.com/pharo-project/pharo/pull/4588 Issue Url: https://github.com/pharo-project/pharo/issues/4537 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #734: FIxesIssue4364
by ci-pharo-ci-jenkins2＠inria.fr Sept. 13, 2019

Sept. 13, 2019

There is a new Pharo build available! The status of the build #734 was: FAILURE. The Pull Request #4570 was integrated: "FIxesIssue4364" Pull request url: https://github.com/pharo-project/pharo/pull/4570 Issue Url: https://github.com/pharo-project/pharo/issues/FIxesIssue4364 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #733: Update-Spec2-and-Commander-2
by ci-pharo-ci-jenkins2＠inria.fr Sept. 13, 2019

Sept. 13, 2019

There is a new Pharo build available! The status of the build #733 was: FAILURE. The Pull Request #4589 was integrated: "Update-Spec2-and-Commander-2" Pull request url: https://github.com/pharo-project/pharo/pull/4589 Issue Url: https://github.com/pharo-project/pharo/issues/Update Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Floating-point numbers with non-decimal radix [Pharo-dev Digest, Vol 77, Issue 5]
by Jim Sawyer Sept. 13, 2019

Sept. 13, 2019

--- Regarding the specification of floating point numbers with radix ~= 10, and in particular the question raised by James Foster(Gemstone). Summarizing the comments from James Foster, Nicolas Collier, Prof Stef Ducasse; followed by some arguments with a lot of hand waving, in order to agree with and support what Nicolas said at the outset: this deserves a new syntax. --- Question: How should it work? The literal 16rFF is 255 (aSmallInteger). Pharo permits lowercase hexadecimal digits, so the literal 16rff is also taken to be 255. The literal 1.23e3 is 1230.0 (aSmallDouble in GemStone). Pharo also permits floating point numbers to have a radix, so that e.g. both 2r1.111e3 and 2r1111 are taken to be 15. This makes certain grammars for numbers ambiguous, because upon encountering either an $E or an $e during the parse of a number, we find two possible interpretations: Is this a hexadecimal digit or an exponent marker? James identified four possible solutions: 1) Distinguish by letter case uppercase $E is a hexadecimal digit lowercase $e is a marker signifying an exponent. 2) Allow exponents on base ten numbers only 3) Distinguish by range radix >= 15 ifTrue: [$e is the hexadecimal digit ]ifFalse: [$e is a marker signifying exponent] 4) Develop a new syntax for floats that does not use either the letter $e or the letter $E to mark an exponent Many implementations of Smalltalk use solution #1, whereas Pharo currently uses solution #3. The result is that any number expressed in other dialects will port to Pharo without issue, while certain expressions for numbers that are recognized in Pharo become ambiguous when ported to other dialects. The most practical âfixâ is for Pharo to adopt the more âpopularâ solution. <tl;dr><outcry> Even so, I submit that this is not the right thing to do. But only because it is a hack, on top of a hack, on top of a design error that went unnoticed for far too long, and really ought to be corrected, for a number of reasons, viz.: 1) The root cause of the problem is an ambiguous grammar. 2) This ambiguity is unique to Smalltalk. It does not occur in any other language, as far as I know. 3) The source of the ambiguity is the design decisionwhich Â introduced a consistent syntax for expressing numbers in Â different bases by directly specifying the desired radix, instead of choosing from the very limited sets of special cases provided by other languages.. One is usually limited to binary, octal, decimal, and hexadecimal, with a unique syntactic form required for expression in each base. We get Bâ01â for binary, \001 for octal, #01 or %01 for hex, and the unadorned 1, left for (the most privileged) decimal form. Introducing a consistent form for specifying alternate bases was itself a great design decision. At the same time, however, a change was introduced which impacted some very long standing properties of numeric representations, and the effect of that change was perhaps not fully considered. As we go about the task of correcting such a latent error, we should Â takeenough time to more fully consider the particulars that brought us here. 4) Smalltalk is a spectacularly consistent design and a spectacularly consistent language to work in.Increasing the consistency of such a language is arguably Â the right thing to do at every opportunity.This is not always themost popular thing to doâbut it is usually the most honorable. And the most useful, in the long term.Practically speaking. 5) Of the four solutions (or cases), we can arguably eliminate three. 1) Distinguish by letter case uppercase $E is a hexadecimal digit lowercase $e is a marker signifying an exponent. 2) Allow exponents on base ten numbers only 3) Distinguish by range radix >= 15 ifTrue: [$e is the hexadecimal digit ]ifFalse: [$e is a marker signifying exponent] 4) Develop a new syntax for floats that does not use either the letter $e or the letter $E to mark an exponent In other domains and languages, numerical values are specified with digits only. In such contexts, using a letter as a syntactic marker is reasonable. Once we adopt the specifiable-radix form (radix)r(rigits)in which numerical values are expressed using digits AND letters, it becomes far less reasonable to use letters as a marker. Case (1) : Differentiation based on the case of letters is fine where the use of letters is pervasive and capitalization is itself generically meaningful, e.g. certain shorthand notations used in regular expressions (%h signifying a match of any lowercase hexadecimal, with %H signifying a match of any uppercase hexadecimal). Whereas using capitalization to distinguish âa valueâ from âa syntactic marke' is a very poor use of character classes, of pixels, and of synaptic gaps, because the association is made without mnemonic support of any kind. Such ârulesâ require rote memorization, i.e. perfect match of an arbitrary fact.The hidden assumption--that any âskillâ involved is both ubiquitous and evenly distributedâ is, alas, unfounded. Case (2) Disallowing exponents for all bases other than 10 is a) inconsistent b) contrary to the point of consistently specifying the desired radix. c) lazy Case (3): Differentiating meaning based on a particular range of valuesmakes for a great explanation of the âdiscoveredâ effect, but is somewhat frighteningto consider using *on purpose*.If we were to adopt anything of this ilk,a better crossover of ranges would be radix <= 10Values are confined to the set of digits (ascii 16r30-16r39) and $E are exponent markers.See also $s, $d, and $q. radix >= 11Letters are required for use as extended values as determined by the radix. We cannot imagine using non-letter characters for this case. Therefore, no exponents for bases above 10. This leaves us with solution (4), create a new syntax for marking the exponent. Because the other solutions are hacks.Practicalâsure.But hacks, nonetheless.Abominable. 7) As Nicolas pointed out, this issue deserves a new syntax. The moment we adopted the specifiable-radix solution, we needed to also abandon the use of the letter $e for marking exponents. Now is our chance to make it right. </tl;dr></outcry> Ideas? -Jim Sawyer ------------------------------------------------------------------------ AVG logo <https://www.avg.com/internet-security> This email has been checked for viruses by AVG antivirus software. www.avg.com <https://www.avg.com/internet-security> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -- This email has been checked for viruses by AVG. https://www.avg.com

4 3

[Pharo 8.0] Build #732: 4574-confusing-comment-in-ThreadSafeTranscriptendEntry
by ci-pharo-ci-jenkins2＠inria.fr Sept. 13, 2019

Sept. 13, 2019

There is a new Pharo build available! The status of the build #732 was: FAILURE. The Pull Request #4581 was integrated: "4574-confusing-comment-in-ThreadSafeTranscriptendEntry" Pull request url: https://github.com/pharo-project/pharo/pull/4581 Issue Url: https://github.com/pharo-project/pharo/issues/4574 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #731: Remove somme Smalltalk references on Spec-2 example
by ci-pharo-ci-jenkins2＠inria.fr Sept. 12, 2019

Sept. 12, 2019

There is a new Pharo build available! The status of the build #731 was: FAILURE. The Pull Request #4567 was integrated: "Remove somme Smalltalk references on Spec-2 example" Pull request url: https://github.com/pharo-project/pharo/pull/4567 Issue Url: https://github.com/pharo-project/pharo/issues/SmalltalkRemovalInSpec2Example Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #730: 4544-MethodPragmaTest-triggers-code-rewrite----commit-to-repository
by ci-pharo-ci-jenkins2＠inria.fr Sept. 12, 2019

Sept. 12, 2019

There is a new Pharo build available! The status of the build #730 was: FAILURE. The Pull Request #4568 was integrated: "4544-MethodPragmaTest-triggers-code-rewrite----commit-to-repository" Pull request url: https://github.com/pharo-project/pharo/pull/4568 Issue Url: https://github.com/pharo-project/pharo/issues/4544 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0