- Pharo-dev - lists.pharo.org

[Pharo 7.0] Build #32: 22750-Add-GTPlayground-classopenUrl
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

There is a new Pharo build available! The status of the build #32 was: FAILURE. The Pull Request #2057 was integrated: "22750-Add-GTPlayground-classopenUrl" Pull request url: https://github.com/pharo-project/pharo/pull/2057 Issue Url: https://pharo.fogbugz.com/f/cases/22750 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Multiline method definition in Tonel
by Mariano Martinez Peck Dec. 12, 2018

Dec. 12, 2018

Hi guys, I was reading the Tonel spec here [1] but it is not clear to me the case of the multiline method definitions. Are those allowed or not? Say I have a method like this: testWith: arg1 with: arg2 with: arg3 ^ 42 Is that valid as Tonel format? Or tonel expects to have method definition in a one liner like: testWith: arg1 with: arg2 with: arg3 ^ 42 Thanks in advance, [1] https://github.com/pharo-vcs/tonel -- Mariano https://twitter.com/MartinezPeck http://marianopeck.wordpress.com

4 4

Fixed by reboot
by Ben Coman Dec. 12, 2018

Dec. 12, 2018

Just reporting a strange occurrence in case anyone sees the same. I was using PharoLauncher fine, then it wasn't. When trying to launch an image it started reporting with "ProcessWrapper newProcess failed..." First time I've ever seen that, and fixed by a reboot, but still strange. There are a couple of other troubles that get fixed by reboot. Anyone have insight into an underlying cause? cheers -ben

3 3

[Pharo 7.0] Build #31: 22752-cleanup-preamble-generation--test-for-method-Sequence
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

There is a new Pharo build available! The status of the build #31 was: FAILURE. The Pull Request #2060 was integrated: "22752-cleanup-preamble-generation--test-for-method-Sequence" Pull request url: https://github.com/pharo-project/pharo/pull/2060 Issue Url: https://pharo.fogbugz.com/f/cases/22752 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

OSSubprocess equivalent in Pharo7?
by Hans-Martin Dec. 12, 2018

Dec. 12, 2018

Hello, I noticed that theOSSubprocess functionality for communicating with OS subprocesses depends on OSSAttachableFileStream which is a subclass of deprecated FileStream (incidentally, the project is not marked as being compatible with Pharo7). The popen()/fgetc() based examples in UNIXProcess are blocking, which is unusable for any but the most basic external command executions. Are there plans to implement a proper replacement in Pharo7? Cheers, Hans-Martin -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 1

[Pharo 7.0] Build #30: 22742 Package ManifestHiedra should be tagged
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

There is a new Pharo build available! The status of the build #30 was: SUCCESS. The Pull Request #2051 was integrated: "22742 Package ManifestHiedra should be tagged" Pull request url: https://github.com/pharo-project/pharo/pull/2051 Issue Url: https://pharo.fogbugz.com/f/cases/22742 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Pharo FIleSystem Compatibility with Gemstone's FileSystemGs
by Guillermo Polito Dec. 12, 2018

Dec. 12, 2018

Hi Reg, Thanks for your email, improving FileSystem is a cool thing ^^. On Tue, Dec 11, 2018 at 8:39 PM Reg Krock via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > Hi, > > I am working on making changes to FileSystemGs to make it work in Gemstone. > > Who is or the the persons to talk to about changes on the Pharo side. > Well, I don't know if there is a single maintainer. I think that myself, Alistair, Sven, and many others can answer to questions on different aspects of file system. Anyways, I'd suggest you just send your emails to this mailing list, the person concerned/interested will answer when possible ;) > > Areas of exploration to date have been: > > 1. Replacement of File with GsFile - in Gemstone we want to use the > native file class. > > How have you made it pluggable? This maybe requires the introduction of a backend or a separate store "GSFileSystemStore"? Does Gemstone require different kind of implementations for different platforms like linux/windows/osx or just a unix-like one is enough? > > 1. Introduction of a FileMode class hierarchy to replace the passing > of they symbols #read and #write. > - Added the proof of concept of FileMode with subclasses to be > passed instead of #write and #read. The classes which have been introduced > are: > > > FileMode > FileAppendMode > FileAppendAndReadMode > FileAppendAndReadBinaryMode > FileAppendBinaryMode > FileReadMode > FileReadBinaryMode > FileReadWriteMode > FileReadWriteMode > FileReadWriteBinaryMode > FileReadWriteTruncatedMode > FileReadWriteTruncatedBinaryMode > FileWriteMode > FileWriteBinaryMode > I like the introduction of objects :) What is the difference between the binary and non binary modes? How do you specify encoding for non binary ones? Or you assume ascii? Also, the fact that the "binary" aspect is repeated all over the hierarchy makes me think they could be composable aspects of a file mode. > > - These classes return the appropriate mode string, (ex: âw+â) and > know if the file is writable.Example of change - the text in blue shows the > change. > > > Exiting format: > (filesystem open: aFileReference path writable: #write) > Well, AFAIU, this is not public API (and it uses booleans to indicate "mode"). Usually end users would simply do: aFileReference writeStream. aFileReference binaryWriteStream. aFileReference readStream. aFileReference binaryReadStream. But yes, I like also to model modes such as truncated, append, "force new". > Proposed format: > (filesystem open: aFileReference path writable: self store > readWriteTruncatedMode) > > The #readWriteTruncatedMode method would return an instance of > FileReadWriteTruncatedMode > > If a form of this proposal were to be adopted, then the appropriate > methods should be renamed to have mode. > As an example, #open:writeable: would become #open:mode: > Well, we could keep the old API and build a higher level one on top, don't we? Do you have your code in a repository we could check? > Thanks for your help. > Thanks to you! Guille > Reg >

2 1

[ANN] Next Pharo Sprint: Dec 21
by Marcus Denker Dec. 12, 2018

Dec. 12, 2018

We will organize a Pharo sprint / Moose dojo Dec 21, starting at 10:00am. (Local Time Paris). Goals of this sprint: â¢ Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come https://association.pharo.org/event-2973628

1 0

[Pharo 7.0] Build #29: 22751-Improve-RFLiteralVariableNode-printing
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

There is a new Pharo build available! The status of the build #29 was: FAILURE. The Pull Request #2058 was integrated: "22751-Improve-RFLiteralVariableNode-printing" Pull request url: https://github.com/pharo-project/pharo/pull/2058 Issue Url: https://pharo.fogbugz.com/f/cases/22751 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #28: 22703-Block-execution-arguments-reification
by ci-pharo-ci-jenkins2＠inria.fr Dec. 12, 2018

Dec. 12, 2018

There is a new Pharo build available! The status of the build #28 was: SUCCESS. The Pull Request #2059 was integrated: "22703-Block-execution-arguments-reification" Pull request url: https://github.com/pharo-project/pharo/pull/2059 Issue Url: https://pharo.fogbugz.com/f/cases/22703 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0