- Pharo-dev - lists.pharo.org

Roassal2 crashing when drawing TRLabelShape
by Oleksandr Zaytsev Sept. 18, 2018

Sept. 18, 2018

Hello, Roassal2 has recently been crashing on my image on every example that includes text. Peter Uhnak helped me discover that it crashes when drawing a TRLabelShape and maybe Cairo doesn't like the new FT plugin. Some experiments: 1. Inspecting an empty view (RTView new inspect) doesn't crash. 2. Everything works well on Pharo 7. My image and crash.dmp can be found in this folder: https://drive.google.com/drive/folders/1lypWVL6VwYfHCqRuXZfnAcA4qZGulDal?us… Oleks

1 0

Re: [Pharo-dev] [squeak-dev] _: in selectors
by Eliot Miranda Sept. 18, 2018

Sept. 18, 2018

On Tue, Sep 18, 2018 at 10:38 AM Levente Uzonyi <leves(a)caesar.elte.hu> wrote: > Hi Eliot, > > That's clearly a bug as the compiler accepts this: > > method: p __: q __: r > ^'cool' > ROTFL > > Levente > > On Tue, 18 Sep 2018, Eliot Miranda wrote: > > > Hi All, > > Pharo accepts > > > > method: p _: q _: r > > ^'cool' > > > > Squeak does not. I have an urgent compelling use case in VMMaker. > Would there be any strong objections to me modifying the Squeak compiler to > accept the above when the allowUnderscoresInSelectors > > preference is in effect? > > _,,,^..^,,,_ > > best, Eliot > > > > > -- _,,,^..^,,,_ best, Eliot

1 0

_: in selectors
by Eliot Miranda Sept. 18, 2018

Sept. 18, 2018

Hi All, Pharo accepts method: p _: q _: r ^'cool' Squeak does not. I have an urgent compelling use case in VMMaker. Would there be any strong objections to me modifying the Squeak compiler to accept the above when the allowUnderscoresInSelectors preference is in effect? _,,,^..^,,,_ best, Eliot

1 0

[Pharo 7.0-dev] Build #1254: 22463 Tag ManifestTextCore and classes in package Text-Core-Manifest
by ci-pharo-ci-jenkins2＠inria.fr Sept. 18, 2018

Sept. 18, 2018

There is a new Pharo build available! The status of the build #1254 was: SUCCESS. The Pull Request #1811 was integrated: "22463 Tag ManifestTextCore and classes in package Text-Core-Manifest" Pull request url: https://github.com/pharo-project/pharo/pull/1811 Issue Url: https://pharo.fogbugz.com/f/cases/22463 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1253: 22456 dynamic left to right columns layout generates an additional unneeded row with null presenters
by ci-pharo-ci-jenkins2＠inria.fr Sept. 18, 2018

Sept. 18, 2018

There is a new Pharo build available! The status of the build #1253 was: SUCCESS. The Pull Request #1803 was integrated: "22456 dynamic left to right columns layout generates an additional unneeded row with null presenters" Pull request url: https://github.com/pharo-project/pharo/pull/1803 Issue Url: https://pharo.fogbugz.com/f/cases/22456 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

UndefinedClasses as first class entities for P7
by Torsten Bergmann Sept. 18, 2018

Sept. 18, 2018

At ESUG 207 there was a presentation about UndefinedClasses as first class entities. According to the slides: https://de.slideshare.net/esug/firstclass-undefined-classes-for-pharo-from-… this was planned for inclusion into Pharo 7. Is this still on the plate? Any status? Thanks T.

4 4

Confused about FileReference read/write streams
by Sven Van Caekenberghe Sept. 18, 2018

Sept. 18, 2018

Hi, Since ever (or as far as I can remember), FileReference made a distinction between read and write streams, see #readStream[Do:] and #writeStream[Do:] - these return a ZnCharacterReadStream and ZnCharacterWriteStream in Pharo 7. Along the same lines, #binaryReadStream and #binaryWriteStream where introduced. However, the first returns a ZnBufferedReadStream (OK) while the latter returns a ZnBufferedReadWriteStream. Why ? I think it would be generally better if a standard ZnBufferedWriteStream where returned. ZnBufferedReadWriteStream is not a very pretty class to say the least, it also strikes me as confusing. What would break if we changed this ? If necessary there could be something like #readWriteStream[Do:] I guess. Sven

2 2

Standardized nomenclature for feature requests
by Esteban A. Maringolo Sept. 17, 2018

Sept. 17, 2018

Hi there, Q: Is there a reason why Pharo (as a project) doesn't follow a standardized nomenclature for features/request as other communities does? So for instance something like PFR-005 (Pharo Feature Request) could be "Truly headless images", PFR-006 "Pharo Bootstrapping", etc. I can't really tell whether this would improve to the overall process, but I wanted to know if this was already debated by the board and dismissed, if it is something that wasn't considered at all, of if we have something equivalent and what it is. Regards, Language examples: JSR (Java Specification Requests) https://www.jcp.org/en/jsr/all PEP (Python Enhancement Proposals) https://www.python.org/dev/peps/ RFC (Rust, Request for Comments) https://github.com/rust-lang/rfcs Technologies: BIP (Bitcoin Improvement Proposal) https://github.com/bitcoin/bips EIP (Ethereum Improvement Proposal) https://eips.ethereum.org/ -- Esteban A. Maringolo

1 0

ZnMimePart Disposition-Content spaces
by Ben Coman Sept. 17, 2018

Sept. 17, 2018

Hi Sven, We encountered a ZnMimePart Content-Disposition header problem with a server expecting a space following the "form-data;" string. The diff here... https://www.diffchecker.com/ETIfCUzx * on the left shows the working request from the default command-line tool * on the right shows the non-working request from Pharo. The specifications are really unclear about the requirement or not for a space, so it may be reasonable to consider the fault lies with the server not being permissive enough, but I notice these examples all have space after semi colons... * https://tools.ietf.org/html/rfc7578 * https://www.ietf.org/rfc/rfc2388.txt so I wonder if this scenario might be widespread (and endemic to Rails apps which this was) and maybe its pragmatic to include the extra spaces to cut off potential issues (it took quite a while to isolate with the live service being HTTPS only.) Steps to reproduce are here... https://github.com/exercism/pharo/issues/96#issuecomment-421224203 In the meantime, once isolated it was simple to work around, but it was almost a show stopper, so I'm interested in your thoughts. cheers -ben

1 0

[Pharo 7.0-dev] Build #1252: 22417 Decide about DateAndTimeDosEpochTest>>testToByDo
by ci-pharo-ci-jenkins2＠inria.fr Sept. 17, 2018

Sept. 17, 2018

There is a new Pharo build available! The status of the build #1252 was: FAILURE. The Pull Request #1810 was integrated: "22417 Decide about DateAndTimeDosEpochTest>>testToByDo" Pull request url: https://github.com/pharo-project/pharo/pull/1810 Issue Url: https://pharo.fogbugz.com/f/cases/22417 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0