There is a new Pharo build available!
The status of the build #1085 was: SUCCESS.
The Pull Request #5386 was integrated: "Hiding the methods from TraitedClass in
Calypso."
Pull request url: https://github.com/pharo-project/pharo/pull/5386
Issue Url:
There is a new Pharo build available!
The status of the build #1088 was: SUCCESS.
The Pull Request #4612 was integrated:
"4611-Lint-clean--categorize-in-Beacon-Core-Tests"
Pull request url: https://github.com/pharo-project/pharo/pull/4612
Issue Url:
Yes, the difference is not good.
Indeed,
Float fmax. "1.7976931348623157e308"
The reason
Number readFrom: '7.5e333'.
gives infinity is actual not because of the reading, but because of
75e332 asFloat.
Which is probably correct.
The failure of
Number readFrom: '7.5e'.
is
There is a new Pharo build available!
The status of the build #1086 was: SUCCESS.
The Pull Request #5396 was integrated: "Migrating the context menu of Keymap
browser to Spec2"
Pull request url: https://github.com/pharo-project/pharo/pull/5396
Issue Url:
"Working with Spec2 and GTK"
Recording:
https://www.youtube.com/watch?v=IVY7TH4MCXI
There is a playlist for all techtalk recordings here:
https://www.youtube.com/playlist?list=PL4actYd6bfnx8l8cqYWhdNB6gJgRvk5sH
actually the problem arose from some old code that I tried to load and
failed to.
So I guess at some point in the past (pharo4 or prior) it was working :
---
PPExpressParserTests>>testReal3
self parse: '-1.1333e' rule: #literal.
self assert: (result value = -1.1333e).
The tests you refer to would basically test Float infinity = Float infinity.
If you change
NumberParser>>#readExponent
"read the exponent if any (stored in instVar).
Answer true if found, answer false if none.
If exponent letter is not followed by a digit,
this is
There is a new Pharo build available!
The status of the build #1087 was: SUCCESS.
The Pull Request #5399 was integrated: "Removed method characterTable. It was
not used "
Pull request url: https://github.com/pharo-project/pharo/pull/5399
Issue Url:
There is a new Pharo build available!
The status of the build #1084 was: FAILURE.
The Pull Request #5390 was integrated: "rollback-bad-comment-when-copying-class"
Pull request url: https://github.com/pharo-project/pharo/pull/5390
Issue Url:
The December newsletter is now online:
https://mailchi.mp/pharo/pharo-newsletter-december-2019
If you have content for the next newsletter -> send me a mail. It starts to get
*really* difficult to not forget something.
Marcus
There is a new Pharo build available!
The status of the build #1089 was: SUCCESS.
The Pull Request #5400 was integrated: "Test for hasLiteralThorough"
Pull request url: https://github.com/pharo-project/pharo/pull/5400
Issue Url: https://github.com/pharo-project/pharo/issues/5154
Build Url:
11 matches
Mail list logo