January 2020 - Pharo-dev - lists.pharo.org

Iceberg: Why create branch when Reviewing a PR?
by Sean P. DeNigris Jan. 13, 2020

Jan. 13, 2020

When reviewing a pull request, when merging, why does Iceberg prepend the repo name to the branch? It seems to require one to manually checkout the issue branch (and remember not to checkout any packages) in order to modify the code, no? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 0

Re: [Pharo-dev] [Vm-dev] [squeak-dev] Reserving/allocating some slots in the specialObjectsArray for DoubleByteArray, WordArray and DoubleWordArray
by Eliot Miranda Jan. 13, 2020

Jan. 13, 2020

Hi Levente, On Mon, Jan 13, 2020 at 2:21 PM Levente Uzonyi <leves(a)caesar.elte.hu> wrote: > Hi Eliot, > > While we're extending specialObjectsArray, it may make sense adding > FloatArray and the currently non-existent Float64Array as well. > Good point. An at:[put:] primitive pair for Float64Array makes sense too. > Levente > > On Mon, 13 Jan 2020, Eliot Miranda wrote: > > > Hi All, > > currently the following slots in the specialObjectsArray are unused > in both Squeak and Pharo (& I suspect Cuis). > > > > newArray at: 32 put: nil. "was the prototype Float" > > newArray at: 33 put: nil. "was the prototype 4-byte LargePositiveInteger" > > newArray at: 34 put: nil. "was the prototype Point" > > > > The specialObjectsArray already contains ByteArray > > newArray at: 27 put: ByteArray. > > > > I would like to have a full set of little-endian unsigned integer > arrays. In Spur Squeak these are ByteArray, DoubleByteArray, WordArray > (Bitmap is big endian), and DoubleWordArray. The VM's at:[put:] directly > supports > > these four at the JIT level giving us efficient unsigned access. There > is also efficient signed access for some signed arrays but these are less > useful (at least in theVM simulator). > > > > I want to make all four unsigned integer array classs available to > plugins etc via the interpreterProxy. So here's a formal request to > reserve these values for use as follows: > > newArray at: 27 put: ByteArray. > > ... > > newArray at: 32 put: DoubleByteArray. > > newArray at: 33 put: WordArray. > > newArray at: 34 put: DoubleWordArray. > > > > _,,,^..^,,,_ > > best, Eliot > > > > > > -- _,,,^..^,,,_ best, Eliot

1 0

[Pharo 8.0] Build #1105: 5474-Still-no-log-when-loading-a-project-via-Metacello
by ci-pharo-ci-jenkins2＠inria.fr Jan. 13, 2020

Jan. 13, 2020

There is a new Pharo build available! The status of the build #1105 was: FAILURE. The Pull Request #5477 was integrated: "5474-Still-no-log-when-loading-a-project-via-Metacello" Pull request url: https://github.com/pharo-project/pharo/pull/5477 Issue Url: https://github.com/pharo-project/pharo/issues/5474 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Embedding Image Example (Win)
by tesonep＠gmail.com Jan. 13, 2020

Jan. 13, 2020

Hi, I have produced an example of using the headless VM to have an embedded image in Windows. The example is hosted in Github (https://github.com/tesonep/pharo-vm-embedded-example) The example is a CMake project to generate a new small executable that uses the VM as a library. Also, it shows how to perform the branding of applications (I have used the same Pharo icon, but we can use anything else). In the example, I am opening one of the SDL2 examples, it opens a window where we can draw in an Athens Canvas. It requires a Cygwin environment, but if you are able to build the headless VM you already have it!. I will do other examples of the use case we are thinking for the headless VM! Cheers, Pablo -- Pablo Tesone. tesonep(a)gmail.com

4 3

[Pharo 8.0] Build #1104: 5097-Creating-a-method-from-debugger-goes-into-infinite-loop-when-typing-something-in-the-class-list
by ci-pharo-ci-jenkins2＠inria.fr Jan. 13, 2020

Jan. 13, 2020

There is a new Pharo build available! The status of the build #1104 was: FAILURE. The Pull Request #5463 was integrated: "5097-Creating-a-method-from-debugger-goes-into-infinite-loop-when-typing-something-in-the-class-list" Pull request url: https://github.com/pharo-project/pharo/pull/5463 Issue Url: https://github.com/pharo-project/pharo/issues/5097 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Mm10s] 2010-01-13
by Esteban Lorenzano Jan. 13, 2020

Jan. 13, 2020

### Last week: - [release] Start Pharo9.0 branch - [release] Fix some issues for Pharo8.0 - [release] Spent a lot of time trying to verify a problem on zerocont (and smalltalkCI) that turned out to be corrected already (but nobody knew it) ;) - [voyage] Fix a cyclic problem on voyage-unqlite. - [Spec2] Fix âcenterâ and âcenterRelativeTo:â properties for Dialogs. ### This week (starting 2019-12-16): - [Release] Organise issues that will enter in P8. - [Release] Prepare release notes - [VM] Check a problem with large installations on AIO/Threaded VM. ### Pipeline - [Release] Pharo 8 Release. - [VM] debug AIO and worker thread VMs on linux and windows.

2 1

about signal
by ducasse Jan. 12, 2020

Jan. 12, 2020

Hi I wanted to explain | semaphore p1 p2 | semaphore := Semaphore new. p1 := [ semaphore wait. 'p1' crTrace ] fork. p2 := [semaphore signal. 'p2' crTrace ] fork. displays p2 and p1. but I would like explain clearly but it depends on the semantics of signal. - ==p1== is scheduled and its execution starts to wait on the semaphore, so it is removed from the run queue of the scheduler and added to the waiting list of the semaphore. - ==p2== is scheduled and it signals the semaphore. The semaphore takes the first waiting process (==p1==) and reschedule it by adding it to the end of the suspended lists. Now this sentence "The semaphore takes the first waiting process (==p1==) and reschedule it by adding it to the end of the suspended lists.â is super naive. Is the semaphore signalling scheduled? or not? signal "Primitive. Send a signal through the receiver. If one or more processes have been suspended trying to receive a signal, allow the first one to proceed. If no process is waiting, remember the excess signal. Essential. See Object documentation whatIsAPrimitive." <primitive: 85> self primitiveFailed "self isEmpty ifTrue: [excessSignals := excessSignals+1] ifFalse: [Processor resume: self removeFirstLink]" I wanted to know what is really happening when a semaphore is signalled. Now resume: does not exist on Processor. I will look in the VM code. S S.

9 36

Interesting bug or feature in exception processing logic
by Denis Kudriashov Jan. 12, 2020

Jan. 12, 2020

Hi. I played a bit with exceptions trying to detect that given block will open the debugger. My idea was to simply catch UnhandledError which normally means that no outer code handles given error and therefore debugger is appeared. For my surprise the following example works from playground but not from the browser editor: [MyTestError signal ] on: UnhandledError do: [ :e | self halt ] In playground you will see the halt. But from the browser the debugger will show MyTestError. After breaking my head I found that there is a difference how scripts are executed in those tools. In Playground it is a deferred action. But in the browser it is evaluated as a deep event processing code (keymap processing) and there is an outer error handler (on: Error do: ) which does some work and passes the exception further (err pass). Following script demonstrates the difference in the error processing logic when there is an outer handler: [ [MyTestError signal ] on: UnhandledError do: [ :e | self halt ] ] on: MyTestError do: [ :z | z pass] Try it from playground. Second line separately will show the halt while all together it will stop at MyTestError signal. Debugging shows that when the outer handler is processed it sets the handler context into the exception and it skips the existing handler for UnhandledError. The question: is it a feature or a bug? Think also how following code should work (unrelated to UnhandledError logic): [ [ 1/0 ] on: MyTestError do: [ :e | self halt ] ] on: ZeroDivide do: [ :z | MyTestError signal ] Currently it will show MyTestError signal. Best regards, Denis

2 14

[Pharo 8.0] Build #1103: 5466-Better-Semaphore-class-comment
by ci-pharo-ci-jenkins2＠inria.fr Jan. 12, 2020

Jan. 12, 2020

There is a new Pharo build available! The status of the build #1103 was: SUCCESS. The Pull Request #5467 was integrated: "5466-Better-Semaphore-class-comment" Pull request url: https://github.com/pharo-project/pharo/pull/5467 Issue Url: https://github.com/pharo-project/pharo/issues/5466 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #5: Fixing FFI Error in Cairo
by ci-pharo-ci-jenkins2＠inria.fr Jan. 11, 2020

Jan. 11, 2020

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

1 0