Re: [Pharo-dev] Some more effort to make Slang and VMMaker work on Pharo [for review]

On 14/05/19 7:59 PM, Guillermo Polito wrote: To do this work - I had to review the AST-to-AST transformation, checking the output, comparing it to what squeak does and so on... Guillermo, This is a superb effort! Thanks. Are you planning to write a paper on this part of your work? A blog?

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

On 23/01/19 2:19 AM, Esteban Lorenzano wrote: $ curl https://get.pharo.org | bash $ ./pharo Pharo.image eval "42 factorial” This should be "curl -L" so that redirects are followed automatically. Regards .. Subbu

Re: [Pharo-dev] ZeroConf trouble (curl/64bit)

--- Begin Message --- On 02/01/19 5:16 PM, Torsten Bergmann wrote: Using ZeroConf on a fresh Ubuntu machine: wget -O- https://get.pharo.org/64 | bash works but curl https://get.pharo.org/64 | bash Does curl -L help? HTH .. Subbu --- End Message ---

Re: [Pharo-dev] Changed #atEnd primitive - #atEnd vs #next returning nil

On Wednesday 11 April 2018 10:38 PM, Alistair Grant wrote: StandardFileStream>>readInto:startingAt:count: assumes that primitiveFileRead will always attempt to read count bytes, but it actually only attempts to read 1. StandardFileStream>>#basicNext uses position < readLimit ifFalse: and do

Re: [Pharo-dev] Changed #atEnd primitive - #atEnd vs #next returning nil

On Wednesday 04 April 2018 09:07 PM, Sven Van Caekenberghe wrote: Good summary, I agree. Still, what are the semantics of #next - does the caller always have to check for nil ? Do we think this is ugly (as the return value is outside the domain) ? Do we then still need #atEnd ? Senders of #nex

Re: [Pharo-dev] Changed #atEnd primitive - #atEnd vs #next returning nil

On Wednesday 04 April 2018 04:06 PM, Nicolas Cellier wrote: IIRC, someone said it is implemented as 'remaining size being zero' and some virtual unix files like /dev/random are zero sized. Currently, for files other than sdio (stdout, stderr, stdin) it is effectively defined as: atEnd := strea

Re: [Pharo-dev] [Testers Required] New FreeType implementation using FFI

On Friday 30 March 2018 06:12 PM, teso...@gmail.com wrote: 32 bits: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/view/change-requests/job/PR-1142/lastSuccessfulBuild/artifact/bootstrap-cache/Pharo7.0-32bit-b8d360a.zip 64 bits: https://ci.

Re: [Pharo-dev] "curl https://get.pharo.org/64 | bash" does not work (on Mac)

On Sunday 25 February 2018 09:54 PM, Bernhard Pieber wrote: Hi all, Here is the output: % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 237 100 2370 0899 0 --

Re: [Pharo-dev] 64 bit VM build problems: gl.h not found, or glRenderer conflicts

On Ubuntu 16.04, I had to use: sudo apt-get install uuid-dev libcairo2-dev libpango1.0-dev libgl1-mesa-dev libgl1-mesa-glx to get all dependencies. This was sometime ago and the change should have made it to build.linux64x64/HowToBuild by now. What exactly is your error message? Regards .

Re: [Pharo-dev] pharo --help returning non-zero exit status

On Sunday 01 October 2017 11:27 AM, Peter Uhnák wrote: Hi, why does executing `pharo --help` return exit status 1? The operation succeeded, so I don't see a reason for a failure return state. This is a bug. See the thread at http://forum.world.st/Re-Pharo-dev-pharo-help-returns-exit-code-1-

Re: [Pharo-dev] About cr and lf

On Friday 04 August 2017 07:11 PM, Damien Pollet wrote: Stream >> newLineFor: platform self nextPutAll: platform lineEnding EOL encoding is a property of a text file and not a platform. While files created on a certain proprietary platforms ;-) may use an encoding that does not make it

Re: [Pharo-dev] Discussing the roadmap

On Friday 07 July 2017 03:26 AM, Eliot Miranda wrote: Let's say that currently the mark-compact collector collects at about 1Gb per second (that's about what I'm seeing on my MacMini for a 600Mb heap, collected and compacted in about 530ms on a 2.3GHz Core i7, = 1.1Gb/s). For the moment let's

Re: [Pharo-dev] FileReference>>/ and path canonicalisation

On Tuesday 27 June 2017 05:01 PM, Sven Van Caekenberghe wrote: A FileReference holds a FileSystem and a Path. A Path is just a collection of elements that leads to a location, the leaf possibly being interpreted as a file with an extension (although that last point is just a convention). It seems

Re: [Pharo-dev] FileReference>>/ and path canonicalisation

On Monday 26 June 2017 01:42 PM, Alistair Grant wrote: 1. Path's are canonicalised during initial creation, but are not when extending the path, i.e. sending #/ E.g. '/dev/shm/d1/d2/../t1.txt' asFileReference " File @ /dev/shm/d1/t1.txt" '/dev/shm/d1/' asFileReference / 'd2/../t1.txt' " File

Re: [Pharo-dev] Doing a pull request

On Friday 16 June 2017 10:57 PM, Esteban Lorenzano wrote: Esteban, Step 2 requires an issue to be created in Fogbugz. It would be nice to do this within Pharo itself. it would be, yes. I have even played with the idea of having a “report bug” button on debugger for years now… but then, someone

Re: [Pharo-dev] Doing a pull request

On Thursday 15 June 2017 08:14 PM, Esteban Lorenzano wrote: 2. work on fix/change 3. commit/push to your repo 4. do a Pull Request once finished. Esteban, Step 2 requires an issue to be created in Fogbugz. It would be nice to do this within Pharo itself. When creating an issue FB requires e

Re: [Pharo-dev] Doing a pull request

On Wednesday 14 June 2017 08:25 PM, Rajula Vineet wrote: Hi, I am a GSoC student working on enhancing pharo command line interface. I was wondering if there is a procedure to make a pull request to the Github repo. It would be really helpful if someone can explain the right way of doing a Pull R

Re: [Pharo-dev] Pharo 7 and changes/sources files

On Friday 09 June 2017 06:38 PM, Guillermo Polito wrote: On Fri, Jun 9, 2017 at 2:51 PM, Yuriy Tymchuk What if the sources is appended to the image file with a special header. New code can relocate this pointer on the fly. The same technique can be applied to changes file too. A small script

Re: [Pharo-dev] remote development via VS Code

On Thursday 08 June 2017 09:15 PM, Eliot Miranda wrote: There are many things one could use this for, but one clear direction, from the success of docker, is to make a Smalltalk image observable and configurable by devops people without having to start up an image and navigate an unfamiliar and f

Re: [Pharo-dev] Problem opening UI saved images

On Wednesday 07 June 2017 02:47 PM, Sven Van Caekenberghe wrote: $ ./pharo-ui one.image Does not open the UI, no window, hangs, no error, nothing. Since the image itself still works, it must be a UI thing. It works as expected on Linux (32-bit code running on 64-bit Ubuntu 16.04). We need to r

Re: [Pharo-dev] please test download for Pharo 6.0

On Wednesday 31 May 2017 07:48 PM, Esteban Lorenzano wrote: Hello, we are getting ready for release. please take a minute to review: http://pharo.org/STAGE.download I uploaded some fixes for review after clearing them through testrunner. But Validation builds failed because of network timeout

Re: [Pharo-dev] please test download for Pharo 6.0

On Wednesday 31 May 2017 07:48 PM, Esteban Lorenzano wrote: Hello, we are getting ready for release. please take a minute to review: http://pharo.org/STAGE.download Quick feedback on Pharo linux/x86_64 on Ubuntu 16.04/64b. I feel the Welcome page should point to HelpBrowser open instead of

Re: [Pharo-dev] basicNew usage pattern

On Sunday 28 May 2017 02:09 PM, Ben Coman wrote: Thanks Subbu. That is a useful insight for me, but is about the implementation. My query was more about senders of basicNew, so is still open if you have an opinion there, or anyone else. It is just a private primitive for creating new instances

Re: [Pharo-dev] basicNew usage pattern

On Saturday 27 May 2017 01:41 PM, Ben Coman wrote: A question arose in Discord regarding #basicNew, to which I felt like the proper answer should be that #basicNew is used only** from the class-side when making custom initializers. (**excepting special meta-handling like by Behaviour) AFAIK, #b

Re: [Pharo-dev] Booklet suggestion

On Thursday 25 May 2017 05:33 PM, Ben Coman wrote: Actually you stimulate my thoughts that the Help file might be a better place for such snippets, so they are always with the image, and don't need to be retyped. Any objections? None. You could gather these under Help->Quick Guide or Help->Tip

Re: [Pharo-dev] Booklet suggestion

Ben, I think there is a deeper need here. Writing good document is hard and keeping it in sync with code is harder still. A book/booklet separates content from the code and being frozen in time faces obsolescence. I would prefer to see a guidebook framework in Pharo that every package author

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

On Tuesday 23 May 2017 08:37 PM, Jan Vrany wrote: Hi, Is it possible to build a file responder right into Pharo and expose packages through WebDAV or FUSE or sshfs service? Then the contents can go directly from RAM (pharo) to RAM (repo server or git) without going through slow disk filesystem.

Re: [Pharo-dev] Class syntax brainstorming

On Monday 22 May 2017 05:32 PM, Denis Kudriashov wrote: package: #MyPackage; tags: #(Core); layout: #MethodDictionaryLayout. How about: properties: { #package->"My Package", ... } A property dictionary would be a better option than named variables as it will not impose a burden on every cl

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

On Sunday 21 May 2017 11:34 PM, Dale Henrichs wrote: As part of his work on Cypress 2.0 Martin McClure is planning on supporting a file per class disk format in addition to the file per method format and possibly a file per package format. I'm not sure whether Martin is at the point where he is

Re: [Pharo-dev] bug in command line handler

On Friday 19 May 2017 05:40 PM, Damien Pollet wrote: I wouldn't want to sound sarcastic, but I'm not sure there is such a concept as "correct" in the context of ANSI escape sequences. Still, according to the legends, 97 is supposed to be high intensity white (for some subset of existing implement

[Pharo-dev] bug in command line handler

All, I found an annoying bug with Pharo's eval command line handler. When it encounters a syntax error, the foreground color is set to red while printing error message, but not restored after (see attachment). I have to reset it every time using "echo -e \e[0m" :-(. I found STCommandLin

Re: [Pharo-dev] Command line save and quit

On Wednesday 17 May 2017 06:53 PM, Damien Pollet wrote: | quit | quit := self commandLine hasOption: 'quit'. (self commandLine hasOption: 'save') ifTrue: [ Smalltalk snapshot: true andQuit: quit ]. quit ifTrue: [ self exitSuccess ]

Re: [Pharo-dev] Current working directory

On Wednesday 17 May 2017 05:08 PM, Rajula Vineet wrote: Hi all, I am working on improving pharo command line as a part of my GSoC project. I have been looking at different current working directory implementations. I have written a blog post

Re: [Pharo-dev] Command line save and quit

On Wednesday 17 May 2017 05:12 PM, Max Leske wrote: Yes. #exitSuccess does a bit more: 1. return an exit code to the command line 2. print a message 3. check if the session has changed 4. allows for overriding and special handling of the Exit exception. You should not assume that nobody needs th

[Pharo-dev] Command line save and quit

Hi, STCommandLineHandler>>#end is defined as: --- | quit | quit := self commandLine hasOption: 'quit'. (self commandLine hasOption: 'save') ifTrue: [ Smalltalk snapshot: true andQuit: quit ]. quit ifTrue: [ self exitSuccess ]. --- C

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

On Tuesday 16 May 2017 04:26 PM, Denis Kudriashov wrote: I checked again. It not works on Raspberry same way: empty string returns. Not know how it would be on other Linux If you run it from command line, does it list the files on the tty? Then it could be a bug in redirectStdout method. HT

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

On Monday 15 May 2017 05:46 PM, Denis Kudriashov wrote: OSSUnixSubprocess new shellCommand: 'ls ~'; redirectStdout; runAndWaitOnExitDo: [ :process :outString | ^outString ]. What exactly are you trying to do? If you want the list of entries in ~ directory, you could use FileDirectory methods:

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

On Monday 15 May 2017 03:31 PM, Denis Kudriashov wrote: It returns empty string and console report: ls: cannot access ~: No such file or directory Any idea why it not works properly? (from command line "ls ~" returns expected files). ~ is a shell language synonym for $HOME. Both are expa

[Pharo-dev] Use of minimal image

Hi, I am tempted ;-) by the following message on Pharo's download page: --- The minimal image is a reduced version of Pharo 7.0 (alpha): You have the most basic environment and you can interact with it via command line. WARNING: For hackers only! --- What kind of hacking has been done with th

Re: [Pharo-dev] ./pharo --help returns exit code 1 on ubuntu

On Friday 05 May 2017 02:11 PM, Andrei Chis wrote: ... ./pharo -help unknown option: -help Common s: --help print this help message, then exit Then `./pharo -help` returns an exit code of 1 on mac/linux while `./pharo --help` returns a exit code of 0 on mac and 1 on linux. It

Re: [Pharo-dev] ./pharo --help returns exit code 1 on ubuntu

On Friday 05 May 2017 03:01 AM, Andrei Chis wrote: Any thoughts or places where I can look? This problem is still in the latest vm. Cheers, Andrei On Thu, Mar 30, 2017 at 9:37 AM, Andrei Chis mailto:chisvasileand...@gmail.com>> wrote: Hi, In an ubuntu installation with the latest vm a

Re: [Pharo-dev] Test and Patch for writeStream error

On Tuesday 18 April 2017 10:51 PM, Alistair Grant wrote: 1. This is assuming that ensureEndsWith: is only used for strings, but the implementation doesn't assume that (I tested it with an Array and it was fine). 2. If you look at existing senders of ensureEndsWith: they check that the string isn'

Re: [Pharo-dev] Test and Patch for writeStream error

On Tuesday 18 April 2017 09:17 PM, Blondeau Vincent wrote: Hi, Thanks for reporting! If you want to contribute and have your fix integrated, I advise you to follow the procedure here: http://pharo.org/contribute-propose-fix Thanks. I opened an issue and posted my fix for review at: https://p

Re: [Pharo-dev] Test and Patch for writeStream error

On Tuesday 18 April 2017 09:51 PM, Alistair Grant wrote: This appears to be changing the meaning of #ensureEndsWith:. The previous meaning was that it always ends with the supplied object. The method name is ambiguous. If the collection is empty does it need an "ending"? All its senders use it

[Pharo-dev] Test and Patch for writeStream error

Hi, I stumbled on an error in WriteStream>>ensureEndsWith: method. The error caused extra blank lines in logs. Attached small changeset fixes it. It also adds a test to catch such errors in the future. With this fix, ./pharo generator.image PharoVMSpur32Builder buildUnix32 gives a compact

Re: [Pharo-dev] Missing VMMaker repo in Pharo 6

On Monday 17 April 2017 11:52 PM, Cyril Ferlicot D. wrote: StartupPreferencesLoader default addAtStartupInGeneralPreferenceFolder: {(StartupAction name: 'Add my repository' code: [ MCRepositor

[Pharo-dev] Missing VMMaker repo in Pharo 6

Hi, I couldn't find the http://source.squeak.org/VMMaker repo in Monticello Browser list of repos. I have to add it to the downloaded image every time to work with VM :-(. Is there any specific reason for not including it by default in Pharo 6 (60465). Regards .. Subbu

Re: [Pharo-dev] [Pharo-users] Pharo 6 snap install

On Monday 17 April 2017 01:04 PM, Luke Gorrie wrote: I wonder if some DWIM would make sense here. For example, my bash wrapper that starts the VM could inspect the image file and decide which VM is appropriate (spur, non-spur, 32-it, 64-bit, etc.) Otherwise the user needs to guess and decipher c

Re: [Pharo-dev] [Pharo-users] Pharo 6 snap install

Luke, I don't see this in the latest binary and I have not adjusted the rtprio figures at all. I can try running some simple tests if you send them to me. $ curl get.pharo.org/64/60+vmLatest | bash file Pharo.image Pharo.image: Smalltalk image Spur 64b +C+NF+Tag (68021) $ prlimit --rtpr

[Pharo-dev] patching vmmaker

Hi, While building the VM from generator.image through eval handler, I noticed spurious blank lines in the log output. I created a changeset that removes these and creates a compact log (all in VMMaker package). My generator.image only throws up local repos for MC. smalltalkhub.com seems to