[Pharo-dev] Re: IMPORTANT: Pharo 12 will enter feature freeze on March 1st

Thanks Esteban. Everybody, please join us in the bugfixing phase to have a robust release! G > El 13 feb 2024, a las 11:25, Esteban Lorenzano via Pharo-dev > escribió: > > Hi, > > The development of Pharo 12 will enter in feature freeze on March 1st and we > plan to have at least one month

[Pharo-dev] Re: About removing class side initialization

> El 31 ene 2024, a las 15:36, Marcus Denker escribió: > > For both #isAbstract and #initialize, one can understand both as cases where > we have to use behavior for something that should actually be a kind o > declarative property of the objects. > > - isAbstract > > This is a property

[Pharo-dev] VM Release 10.0.8

Hi all, TL;DR; update your launcher VMs and your download scripts! There is a new VM version: release 10.0.8 which fixes, among others, a performance regression that showed in some cases that overly relied on the interpreter. See below the changes log, and for those interested, the fix for

[Pharo-dev] Re: Next Pharo sprints

Ha, of course, I forgot that. I’ll update the post: 29/09 27/10 24/11 22/12 > El 14 sep. 2023, a las 12:26, Noury Bouraqadi escribió: > > Hi, > > I'd like to attend. When is the next one ? > > Noury > > On Wed, Sep 13, 2023, 09:42 Guillermo Polito <mailto:gui

[Pharo-dev] Next Pharo sprints

Hi all, For those who would like to participate, we are opening the Pharo sprints we do at Lille every last friday of the month. Feel free to contact us if you would like to participate, drop an email or a message somewhere :) More info in the link below!

[Pharo-dev] Re: Pharo @ ESUG'23

Of course, better if I send the right link :) https://thepharo.dev/2023/09/13/pharo-esug23/ > El 13 sep. 2023, a las 09:39, Guillermo Polito > escribió: > > Hi all, > > for those that were not at ESUG, we did a small write-up about the Pharo > activity at the c

[Pharo-dev] Pharo @ ESUG'23

Hi all, for those that were not at ESUG, we did a small write-up about the Pharo activity at the conference. https://wordpress.com/post/thepharo.dev/1957 Cheers, Guille

[Pharo-dev] Re: [Pharo-users] The results of the Pharo Browser usage survey are available

Thanks Koen! It’s fun to read in detail :) So, what’s the action plan? > El 5 sep. 2023, a las 22:10, Koen De Hondt > escribió: > > Dear Pharo users and developers, > > Last week at ESUG’23 I presented the results of the survey on the usage of > the Pharo Browser. Half an hour was not

[Pharo-dev] Re: Compiling Pharo VM used for P8

Hi Jan, could you share a link to the repo/commit you’re building? Have you tried with this tag? https://github.com/pharo-project/pharo-vm/tree/v8.6.1 G > El 1 sep. 2023, a las 14:32, Jan Vraný escribió: > > Hi, > > I'm trying (and failing) to (re)compile Pharo VM used for P8, more >

[Pharo-dev] VM Release 10.0.6 on the pipe

Hi all, This email is to tell you that there is a new VM release on the CI pipe, with many fixes and improvements. This release will be available for versions of Pharo 11 and above. Improvements in build environment * Update build environment for Pharo 10 vm branch by @guillep in

[Pharo-dev] Fun with dates

Try to guess what each of the following lines of code do: '''/5%9/$#=7*''*(?&&)58-,=93/1(0 1&<"1%?#$-::#)' asDate. '*%!@$4*4#!$!.&0-";)7.<7?%(; $535(0536.%#56&++''3!%0/' asDate. '/-@+%3:3.''9"04=. @5+$;"& (6.-,?@*6"?43@@>*>:' asDate. '1(%&0:19)) 7-?1.8;=?8+!&42-(?#>357).!=21603*

[Pharo-dev] Re: [ANN] CBOR for Pharo

Thanks Sven :) > El 23 jun. 2023, a las 00:06, stephane ducasse > escribió: > > Super nice > for a moment I thought that you forgot the final G of the name :) > >> On 21 Jun 2023, at 11:25, Sven Van Caekenberghe wrote: >> >> [ANN] CBOR for Pharo >> >> https://github.com/svenvc/CBOR >> >>

[Pharo-dev] Re: [ANN] Pharo 11 Released !

++1 !! :) > El 11 may. 2023, a las 14:02, Gabriel Cotelli escribió: > > Congratulations on the new release. Now it's time to adapt the libraries and > check that continue working with this version :P > > I think you need to update also > https://github.com/pharo-project/pharo/releases >

[Pharo-dev] Re: Pharo contribution Jenkins end of service

Thanks Christophe! > El 11 may. 2023, a las 11:32, Christophe Demarey > escribió: > > Hi all, > > Some years ago, we provided a Jenkins instance to check the health / quality > of projects that are not in Pharo core but important for the community: > https://ci.inria.fr/pharo-contribution/

[Pharo-dev] Ephemerons in P11

Hi all, For those that may not be following the day-to-day development, you may be interested in that Ephemeron support is now enabled in Pharo 11 for one week or so (VM version 10.0.0, Image build 627). Here are some takeaways and actions to take you may be interested in: To get the latest

[Pharo-dev] Re: Pharo VM Release - v10.0.0

PR has been green for two weeks waiting for a review https://github.com/pharo-project/pharo/pull/12042 And the Phep was updated taking (almost) all comments into account https://github.com/pharo-project/pheps/pull/19 :) > El 13 mar. 2023, a las 20:32, s...@clipperadams.com escribió: > >

[Pharo-dev] Re: PhEP: Underscores in Numeric Literals

+1 > El 13 feb. 2023, a las 20:37, Daniel Slomovits > escribió: > > Seems reasonable to me. I was just wishing for such a thing for exactly the > reason you mention (keeping track of zeroes in large integer literals). > AFAICT you've done a pretty good job laying out the possible error >

[Pharo-dev] Re: Pharo11 32 bits images missing?

Nope, this is most certainly a bug, thanks for raising the flag! > El 22 ene. 2023, a las 18:10, Pierre Misse Chanabier > escribió: > > Hello, > > Apparently Pharo 11 does not build 32 bit images [1]. > Did I miss an announcement? > > Pierre > > http://files.pharo.org/image/110/

[Pharo-dev] Re: Linux OBS builds updated

Hi Pavel, thanks for looking into this. Why not adding those mappings in the table so they are mapped by `self mapSpecialCharacter: keysym sym` ? G > El 6 ene. 2023, a las 08:53, Pavel Krivanek > escribió: > > Hi, > > that is interesting issue. I have here a notebook with Numpad where I

[Pharo-dev] Draft Phep on new Finalization

Hi all, I’ve drafted a phep proposal for the new finalization mechanism, so we can discuss it here! https://github.com/pharo-project/pheps/pull/14 A proposal describing a new finalization mechanism for Pharo with the following properties:

[Pharo-dev] Re: Pharo VM Release - v9.0.21

Thanks Pablo!!! > El 12 dic. 2022, a las 14:30, teso...@gmail.com escribió: > > Hello, > I have released a new version of the Pharo VM for Pharo 9, Pharo 10 and > Pharo 11. This VM is accessible right now from Zero-Conf, updating it in the > Pharo Launcher or using the usual downloads (as

[Pharo-dev] A/B Testing the latest VM on the Pharo repository PRs

Hi all, TL;DR; I propose we start testing the latest VMs on PRs to the Pharo repository in a "semi-random” way. The idea is to earn some confidence while having a small impact on all of you. We need to slowly start pushing the latest VM version, right now hosted in the pharoX branch of

[Pharo-dev] Re: Status update of Libgit2 and CI issues

nd > escribió: > > > Thank you for the update. > I followed the thread and I imagine it was not easy to work on this problem. > > Best regards, > > Hernán > > > El vie, 19 ago 2022 a las 16:45, Guillermo Polito ( <mailto:guillermopol...@gmail.com>>) escri

[Pharo-dev] Status update of Libgit2 and CI issues

A couple of weeks ago we got reported a big recurrent failure on CI jobs while cloning using iceberg/libgit https://github.com/pharo-project/pharo/issues/11481. TL;DR; So far (Friday ~17h Paris time) we managed to get everything up and running. A new VM is being released by our CI, all pull

[Pharo-dev] MPLR 2022 -- Call for Participation

Call for Participation MPLR 2022 - 19th International Conference on Managed Programming Languages & Runtimes September 14-15, 2022 in Brussels, Belgium

[Pharo-dev] Re: [Compiler] Variables in DoIts

Wow, I think that’s super cool!! And a worthy direction to explore. Having the surrounding code would give developers a lot more context!! > El 24 jul 2022, a las 20:47, Denis Kudriashov escribió: > > Hi. > > сб, 25 июн. 2022 г. в 13:48, Guillermo Polito <mailto:guiller

[Pharo-dev] Re: [Compiler] Variables in DoIts

> El 25 jun 2022, a las 14:38, Denis Kudriashov escribió: > > Now we can play with other interesting options. > We can completely remove reformatting of code for DoIts and make the > debugging more "transparent" for users: > > > > Notice there is no DoIt header anymore . What is selected

[Pharo-dev] Re: This week (18/2022) on the Pharo Issue Tracker

Thanks Marcus! > El 6 may 2022, a las 8:15, Marcus Denker escribió: > > We merged 8 PRs and fixed 9 Issue tracker entries. > > There are more PRs ready to be reviewed! > https://github.com/pharo-project/pharo/pulls > > Even a reviews for trivial changes (like improvements in comments,

[Pharo-dev] Re: [ANN] Pharo Launcher 3.0 released!

Thanks Christophe, this is super work :) > El 14 abr 2022, a las 14:26, Christophe Demarey > escribió: > > Hi all, > > Pharo Launcher 3.0 has just been released! It is available from > http://pharo.org/download . > It is based on latest Spec2 and Pharo 10 image. >

[Pharo-dev] PharoDays'22: Inscriptions are open!

Pharo Days March 3rd and 4th, Lille, France https://days.pharo.org/ Inscriptions are open! Do not miss the opportunity to meet the Pharo

[Pharo-dev] [Pharo Days'22] Call for participation

Pharo Days March 3rd and 4th, Lille, France https://days.pharo.org/ Do not miss the opportunity to meet Pharo and its community!

[Pharo-dev] Re: [lse-consortium-eng] Array sum. is very slow

Yet, be careful, that way of benchmarking will have a lot of variation and noise. Remember there is an OS, other apps open, even the CPU getting hot/cold can introduce performance differences... At least, that snippet should be run so many times (I do 100 iterations in general), and the averages

[Pharo-dev] Re: Array sum. is very slow

lone developer in my spare time. So my apologies for any ugly code. > > > Thanks for your help. > > Jimmie > > > On 1/6/22 15:07, Guillermo Polito wrote: >> Hi Jummie, >> >> Is it possible that your program is computing a lot of **very** large >&g

[Pharo-dev] Re: Array sum. is very slow

Hi Jummie, Is it possible that your program is computing a lot of **very** large integers? I’m just trying the following with small numbers, and I don’t see the issue. #sum executes on a 28k large collection around 20 million times per second on my old 2015 i5. a := (1 to: 28000). [a sum]

[Pharo-dev] Re: Hardening Zinc's Core HTTP Server

Thanks Sven, 51 days uptime is super encouraging :) > El 30 nov 2021, a las 17:45, Sven Van Caekenberghe escribió: > > Hi, > >> On 29 Oct 2021, at 20:42, Sven Van Caekenberghe > > wrote: >> >> Here is yet another update: >> >> The instances >> >> - On Amazon AWS:

[Pharo-dev] Re: Ephemeron Status?

Hi Sean, Ephemerons are working well in Pharo 9, as far as I am concerned, at least from the VM side. We have thoroughly tested them and stressed the implementation with several thousand ephemerons. And we have used them to prototype a precise memory profiler with a student during the summer

[Pharo-dev] Re: Serious NetNameResolver regression

Hi all, it seems we need a new VM release. The issue seems fixed since ~6 months ago https://github.com/pharo-project/opensmalltalk-vm/commit/bff77946691617acce104d8f38d60242fa1cc2bb Pablo is updating the stable VMs just in this moment. G > El 16 jul 2021, a las 12:07, Sven Van Caekenberghe

[Pharo-dev] Re: Broken window alert

ob/Pharo9.0/1285/> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo9.0/1284/ <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo9.0/1284/> > >> On 6 Apr 2021, at

[Pharo-dev] Broken window alert

Hi Guys, With Pablo we were discussing that it would be nice to stop with the integrations until we fix the broken tests. We have crossed the 20 broken tests for more than 20 builds. We should put some energy in fixing those, but we are afraid that if we continue this way, eventually it will

[Pharo-dev] Re: PharoJ now available for Pharo10

> El 1 abr 2021, a las 13:38, Noury Bouraqadi escribió: > > Hi everyone, > > We continue to make progress during our weekly coding sessions. We are glad > to announce that this week we made a huge leap forward. Now PharoJS is > available for Pharo 10. To install it, run the following

[Pharo-dev] Re: Pharo - GSOC 2021

Nice!!! Thanks everybody!!! > El 11 mar 2021, a las 17:38, Hernán Morales Durand > escribió: > > Congratulations :-) > > Hernán > > El jue, 11 mar 2021 a las 7:34, Serge Stinckwich ( >) escribió: > Dear all, > > great news I want to share with you: Pharo

[Pharo-dev] Re: Cmd-line (headless) Pharo Launcher - structure of commands

Hi David, I think this is cool :) The things you describe are what I was having in mind too. The commands I use the most from the UI are: - create/delete an image - launch it :) About the design of the command line, have you checked Clap? It should provide support for parsing command line

[Pharo-dev] Re: Progress Report -> Refactoring Project - ( February 1 - 5 )

Hi Tim, you may want to have a look at Preserving Instance State during Refactorings in Live Environments https://hal.archives-ouvertes.fr/hal-02541754/document G > El 13 feb 2021, a las 9:46, Tim Mackinnon escribió: > > I never thought of that implication - if ivars are proper objects (is

[Pharo-dev] Re: Pharo 8 Image blows up after restart

Cool :) Glad to help > El 9 dic 2020, a las 10:46, Sabine Manaa escribió: > > Hi Eliot, hi Guille, > > you saved my day! > > starting from command line and killing with SIGUSR1 showed the stack below. > > Starting the image without mongoservice running avoids the blowup. > > Then, saving

[Pharo-dev] Re: Pharo 8 Image blows up after restart

Another idea is that as soon as you detect the problem, you send the SIGUSR1 signal to the VM from another terminal. $ kill -SIGUSR1 thePID When the Pharo process receives the SIGUSR1 signal it will output a dump with - the C execution stack - the Pharo execution stacks Maybe for debugging

[Pharo-dev] Re: This week (49/2020) on the Issue Tracker

> El 7 dic 2020, a las 17:02, Sean P. DeNigris escribió: > > Wow! Impressive list :) > > > Marcus Denker-4 wrote >> - Activation in single click (which triggers column expansion) is now >> default for inspections (it was double click, but it felt weird). > > -1 on this. The problem with

[Pharo-dev] Re: [ANN] New UI renderer with Hi-DPI support (Beta testing)

The slides are here, I don’t know about any recordings, maybe Ronie will repeat it and a record it later? http://rmod-files.lille.inria.fr/Team/Presentations/2020-form-scene-graph-Salgado.pdf > El 30 nov 2020, a las 11:09, Ben Coman escribió: > > Was there any recording? > > On Thu, 26 Nov

[Pharo-dev] [ANN] Smalltalkhub Readonly Migration tuesday 8hs - server maintenance / migration

Hi all, We wanted to announce that, as announced previously, Smalltalkhub is going read only from tomorrow, 8h central Europe time. This means the service could be down for a couple of hours until the sync of data is done. Keep tuned, Guille and Christophe in behalf of the RMoD team

Re: [Pharo-dev] [rmod] [Pharo-users] [ANN] SmalltalkHub Deprecation Notice

Hi Renaud, > El 3 abr 2020, a las 16:27, Renaud de Villemeur > escribió: > > Hi Guille. > > It's a good news to see the community is moving forward. > > What would be the impact on Pharo catalog ? The instruction still advise to > upload information to smalltalkhub: >

[Pharo-dev] [ANN] SmalltalkHub Deprecation Notice

SmalltalkHub Deprecation Notice SmalltalkHub is now getting old and it is time to deprecate it. We plan to replace it by a static file server during 2020. The public data will still be readable and consumable from monticello clients, but modifications will not be allowed in the near future.

[Pharo-dev] [ANN] Complishon: efficient heuristics for code completion

Hi all, Since yesterday, Pharo 9 contains a new alternative code completion engine. The idea behind this engine is to be pluggable, to be efficient and to be more accurate through the introduction of heuristics. The completion engine implements a couple of nice heuristics, like - chances are

[Pharo-dev] Today 27/03/2020: Pharo Sprint!

Hi all, Today we are having a dematerialized Pharo sprint. # What is this sprint thingy? We join. We fix bugs. We discuss about fixing bugs. We add documentation. We review issues and pull requests. We make Pharo better for us and for everybody else :). # How is this sprint thing going on?

Re: [Pharo-dev] Is HiExampleTest a fleaky test?

I confirm it was a timeout. The jenkins report has the information in the XML, but the app does not show it. https://github.com/pharo-project/pharo/issues/5930 <https://github.com/pharo-project/pharo/issues/5930> > El 18 mar 2020, a las 9:29, Guillermo Polito > escribió: > &g

Re: [Pharo-dev] New VM promoted to Stable for Pharo 8

https://github.com/pharo-project/opensmalltalk-vm/issues/69 > El 3 mar 2020, a las 19:11, Sven Van Caekenberghe escribió: > > A side note, VM version strings are an absolute disaster for end users, it is > simply impossible to talk

[Pharo-dev] [ANN] uFFI Booklet v1.0

Hi all, We have been working a lot in the last months in the documentation of uFFI, and we are happy to announce a first stable version of it that you’ll find in a link below :) The booklet talks about uFFI, how to use it, how marshalling works, how to use structures, unions, etc. And it is

Re: [Pharo-dev] Iceberg Bug? Branches with $/

Hi all, Iceberg supports branches named with slashes. It can pull, push, merge, checkout… IIRC, what does not properly work is metacello support regarding it, because the parser of metacello urls may consider those extra “url path elements” part of the directory to fetch the project. Guille

Re: [Pharo-dev] Fwd: [GitHub] Deprecation Notice

ing else. > > "We will deprecate basic authentication using password” > > S > >> On 22 Jan 2020, at 07:47, Guillermo Polito wrote: >> >> Hi, >> >> I believe that when cloning a repository using the Github tab from iceberg, &

Re: [Pharo-dev] Fwd: [GitHub] Deprecation Notice

Hi, I believe that when cloning a repository using the Github tab from iceberg, iceberg makes a request to ask github for that project’s meta-data. This query identifies if the cloned repository is a fork of another repository or not, and in case it is a fork, correctly pre-configure the

[Pharo-dev] Short Survey about automatic deprecation rewrites

Hi all, We would like to share with you a short survey about the automatic deprecation rewrites that have been around since Pharo 6. It will be super useful for us to enhance the support for migrations. We estimate it will take ~< 3 minutes to fill. This survey is aimed at people both *using*

Re: [Pharo-dev] Pumping FFI documentation

tried removing it and the pdf compiles neatly. Another solution is to escape the dashes \-\- to get the double dash output in the final text (which in latex renders as a long dash IIRC). I’ve fixed it in the latest commit. > El 30 sept 2019, a las 17:28, Brainstorms escribió: > > G

Re: [Pharo-dev] Pumping FFI documentation

> El 1 oct 2019, a las 8:45, ducasse escribió: > > Guille can you merge in the master like that I can read it and check without > messing everything up. Done > > >> On 30 Sep 2019, at 10:35, Guillermo Polito wrote: >> >> >> >>>

Re: [Pharo-dev] Pumping FFI documentation

ocally, probably there is a silly pillar syntax error somewhere that generates broken latex... > > -Ted > > > > Guillermo Polito wrote >> Hi Ted, >> >> I split this in a separate thread to avoid noise :) >> >>> El 23 sept 2019, a las 23:14

[Pharo-dev] Pumping FFI documentation [WAS] FFI beginner question

Hi Ted, I split this in a separate thread to avoid noise :) > El 23 sept 2019, a las 23:14, Brainstorms escribió: > > Guillermo, > > I'm interested in helping, but at this point, I think I'd be most helpful > working at improving documentation (mainly editing) rather than working on > Pharo

Re: [Pharo-dev] [Pharo-users] FFI beginner question

ithub.com/pharo-project/pharo/issues/4695> Of course, if somebody wants to help, you’re welcome to :) Guille > El 23 sept 2019, a las 13:59, Guillermo Polito > escribió: > > Just more detail into it: > > - the source code of the booklet, written in Pillar, resi

Re: [Pharo-dev] TraitedMetaclass / Behaviour bug?

> El 18 sept 2019, a las 15:05, Alistair Grant escribió: >>> >>> TraitedMetaclass stores methods in two different instance variables: >>> >>> - methodDict (inherited from Behavior) >>> - localMethods >>> >>> And the same method can be different in each dictionary. >> >> Yes, trais actually

Re: [Pharo-dev] TraitedMetaclass / Behaviour bug?

About bug1) I’ve found that Calypso query scopes use sometimes #methods and sometimes #localMethods ClyLocalClassScope >> methodsDo: aBlock self classesDo: [ :eachClass | self metaLevelsOf: eachClass do: [ :concreteMetaLevelClass |

Re: [Pharo-dev] TraitedMetaclass / Behaviour bug?

Hi Alistair, we are checking this with Pablo here, some questions inline > El 18 sept 2019, a las 11:04, Alistair Grant escribió: > > Hi Everyone, > > TraitedMetaclass stores methods in two different instance variables: > > - methodDict (inherited from Behavior) > - localMethods > > And the

Re: [Pharo-dev] Slot definition API?

> El 9 sept 2019, a las 9:57, Marcus Denker escribió: > > I will have a look, but I feel that we should first get the Composed Slots > into the image > as they will change everything again. Marcus, how much time could it take you to have a mature version we can test and try? I'd avoid

Re: [Pharo-dev] Slot definition API?

Th¡¡ > El 8 sept 2019, a las 23:48, Torsten Bergmann escribió: > > Hi, > > I'm not too deep in the CDSlotNode and related - but I wonder why we need the > specific #=> selector and > >slotName => Definition > > mapping form in the definition at all. What are the benefits of the >

Re: [Pharo-dev] Slot definition API?

> El 8 sept 2019, a las 17:59, ducasse escribió: > > > >> On 8 Sep 2019, at 09:17, ducasse wrote: >> >> Hi >> >> I’m fixing the class definition parser and I have a question. >> >> I’m stabilizing the API of CDSlotNode >> >> >> 1 ‘first' => LazyClassVariable default: 5. >> 2 ’second'

Re: [Pharo-dev] Slot definition API?

> El 8 sept 2019, a las 17:55, ducasse escribió: > > > >> On 8 Sep 2019, at 10:15, teso...@gmail.com wrote: >> >> Hi, I really like the idea of returning a node object for the initialization. >> From seeing the class definition, I think we should assume that: >>

Re: [Pharo-dev] possible Windows Update "1903" Iceberg problem

versions. > These libraries are available in > https://drive.google.com/open?id=1fwAVyrEEXkGOAuyAh1wASRRSv3SjZ3R1 > The idea is to start testing them while we are working on a new > release of the VM. > > Cheers, > Pablo > > On Wed, Sep 4, 2019 at 10:05 AM

Re: [Pharo-dev] possible Windows Update "1903" Iceberg problem

Hi all, Sorry for not communicating better :). We know this is an important issue and we did move it to top priority even prior to this email ;). Doru, to answer you, what people can do for the moment is to test what we are going to propose in a couple of hours in your windows machines. With

Re: [Pharo-dev] [Weekend Procastination] what the new minheadless opens as posibilities :D

> El 26 ago 2019, a las 14:08, ducasse escribió: > > Hi guille > >> Procastination 1: Render the world fully in athens (instead of a middling >> bitmap) to have an idea of the effort to get fast to hdpi >> >> What you see here is a world drawn completely in athens in minheadless, >>

Re: [Pharo-dev] [Pharo-users] Information on Spec development

Thanks for pushing this Cyril! This will let us move forward with Iceberg too :) > El 13 ago 2019, a las 12:15, Cyril Ferlicot > escribió: > > On Thu, Jun 20, 2019 at 5:29 PM Cyril Ferlicot > wrote: >> >> Hello everyone! >> >> This is an important update

[Pharo-dev] Some new bindings for native emulation stuff

Hi everybody, I’ve been playing around with machine code simulation this last week and I’ve made bindings for the unicorn library and the llvm disassembler: https://github.com/guillep/pharo-unicorn https://github.com/guillep/pharo-llvmDisassembler

Re: [Pharo-dev] proposal - contribution workflow - PR-only for pre-fixed Issues

Hi Ben, I agree. In general, I too do see that this artificial separation is adding little/no value. This would also simplify a bit the build scripts: instead of having to parse the PR name to get the issue number, we could just use the available PR number. > El 14 jul 2019, a las 10:30, Ben

Re: [Pharo-dev] Default line endings while writing to a file stream

> El 2 jun 2019, a las 20:45, ducasse escribió: > > Sven > > why not having this as extension. I’d even propose to have it by default: a FileReference writeStream can return a ZnNewLineWriterStream wrapping the corresponding stream. By default it can be configured with the system’s

Re: [Pharo-dev] Calypso idea - inherited tests

Hi Ben, > El 29 may 2019, a las 3:46, Ben Coman escribió: > > (Just a quick share from work before that neuron goes back to sleep and I > forget it...) > > When a number of domain substitute classes need to satisfy the same tests, > its useful to define these in a superclass and have

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

Hi Subbu, I do not believe this deserves a paper :P. At most a blogpost. What I can do quickly here is to draft the “methodology” I followed by instinct, but that can be reproduced by anyone. 1) generate sources from pharo 2) try to compile (and run) 3) in case of failure, make a diff with the

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

Hi Eliot, > El 15 may 2019, a las 3:20, Eliot Miranda escribió: > > Hi Guille, > > On Tue, May 14, 2019 at 7:30 AM Guillermo Polito <mailto:guillermopol...@gmail.com>> wrote: > > - I had to review the AST-to-AST transformation, checking the output, > compar

Re: [Pharo-dev] Metacello/Iceberg detached head of cascade loaded requirements

Hi Ben, I’ll complement a bit Gabriel’s answer. See inline > El 11 may 2019, a las 10:39, Ben Coman escribió: > > I have a query about "Detached HEAD" status after a Metacello/Iceberg > cascade load of required packages. Starting with the general questions... > Is that a common status for

Re: [Pharo-dev] how implement isAbstract?

Hi Andrei, Doru, Sorry for the late reply, I've been away on vacations last week :). Denis introduced originally the behaviour making classes return true for #isAbstract only when they had #subclassResponsibility methods in them. Originally, if I'm not mistaken, it was to introduce the `should

Re: [Pharo-dev] FreeType and the over amorous glyphs (overlapping)

So, this morning we have been working on validating this hypothesis and making a meaningful and reproducible test for it. I'm just the messenger here because Pablo who has done most of the job is shy. ## The main story Since we are working with concurrency and non-determinism, we have designed a

Re: [Pharo-dev] FreeType and the over amorous glyphs (overlapping)

We need a new stable vm... On Wed, Apr 10, 2019 at 4:16 PM ducasse wrote: > Pablo I tried the file you sent and I imported it in the PharoLauncher and > I could not handle file. > I got a File class bad argument and after I could not use iceberg. > > Stef > > > On 10 Apr 2019, at 15:38,

Re: [Pharo-dev] IceGenericError: failed to stat file, Pharo LAUNCHER images and long file names on Windows

Hi, On Mon, Apr 1, 2019 at 9:26 PM Torsten Bergmann wrote: > If one downloads images with Launcher on Windows and accepts default names > like "Pharo 7.0 - 32bit (stable)" this will end up in path names like > >"C:/Users/Admin/Documents/Pharo/images/Pharo 7.0 - 32bit (stable)" > > The dot

Re: [Pharo-dev] Green tests

On Tue, Apr 2, 2019 at 5:36 PM Marcus Denker wrote: > > > > On 2 Apr 2019, at 17:30, ducasse wrote: > > > > Cool and thanks! > > I love this green bar and I will try to keep it green. > > Do you know if the test writing by pierre should be pushed in Pharo > because I have the impression that

Re: [Pharo-dev] Green tests

On Tue, Apr 2, 2019 at 5:31 PM ducasse wrote: > Cool and thanks! > I love this green bar and I will try to keep it green. > Do you know if the test writing by pierre should be pushed in Pharo > because I have the impression that they will be red first > Short answer: no :). Long answer: I've

[Pharo-dev] Green tests

Hi all, In a couple of minutes I've made some (not complicated) fixes to make Rubric tests green again: https://github.com/pharo-project/pharo/pull/3129 This is of course not a super Rubric enhancement (for which I've opened another issue requesting some missing feature

Re: [Pharo-dev] New stable VM for Pharo8?

n the meanwhile, using the build I say in the email above may suffice us all I think ^^. > > Stef (back writing research proposal…..) > > On 2 Apr 2019, at 13:40, Guillermo Polito > wrote: > > Hi all, Esteban, > > In the last sprint with Pablo and Pierre we have d

[Pharo-dev] New stable VM for Pharo8?

Hi all, Esteban, In the last sprint with Pablo and Pierre we have detected several misbehaviours with files. The issue was particular reproducible when trying to run iceberg tests: the VM kind of ran out of slots for opening files. The strangest thing is that the leaks seemed to happen when

Re: [Pharo-dev] Missing tests for FFI in CI

Hi Stephan, Le jeu. 21 mars 2019 à 21:39, Stephan Eggermont a écrit : > ducasse wrote: > > Hello Stefan > > > > Can you report the exact call you were doing? > > I talked with G and Pablo and the bug they fixed is not the same. > > Now they would like to experiment and write tests for all the

Re: [Pharo-dev] About a better filedialog

YES! On Mon, Mar 18, 2019 at 11:13 PM ducasse wrote: > Yes I had to rename ComposableModel into ComposablePresenter so this is > probably that > > On 18 Mar 2019, at 23:09, Peter Uhnak wrote: > > Thanks Stef! > > The build is failing for Pharo 6.1 for some reason (I can't reproduce it >

[Pharo-dev] [ANN] Iceberg 1.5.7 (pharo6 is back)

Hi all, I'm on vacations, so I've produced a new patch version of Iceberg :). This version restores compatibility with Pharo6, which was broken since latest changes done for Pharo7 64bit support. https://github.com/pharo-vcs/iceberg/releases/tag/v1.5.7 I hope people still using Pharo6 find this

Re: [Pharo-dev] Pillar branch names (was: ConfigurationOfGrease for Pharo8)

On Sat, Feb 9, 2019 at 5:32 PM Alistair Grant wrote: > Hi Guille, > > On Mon, 4 Feb 2019 at 09:43, Guillermo Polito > wrote: > > > > On Mon, Feb 4, 2019 at 9:28 AM Alistair Grant > wrote: > >> > >> Hi Stef, > >> On Mon, 4 Feb 2019 at 09

Re: [Pharo-dev] Esteban's ChangeLog week of 4 February 2019

On Mon, Feb 11, 2019 at 9:54 AM Norbert Hartl wrote: > > > Am 11.02.2019 um 09:22 schrieb Esteban Lorenzano : > > > > On 11 Feb 2019, at 09:20, Nicolas Cellier < > nicolas.cellier.aka.n...@gmail.com> wrote: > > > > Le lun. 11 févr. 2019 à 08:45, Norbert Hartl a > écrit : > >> >> >> > Am

Re: [Pharo-dev] iceberg: merging branches just at the git level without changing code in the image

Hi, On Mon, Feb 4, 2019 at 6:19 PM Andrei Chis wrote: > Hi, > > Currently in Iceberg to merge a branch into another, we need to checkout > the branch into which we want to merge and then do the merge. > For the moment it is done that way because - every commit is first written in disk before

Re: [Pharo-dev] ConfigurationOfGrease for Pharo8

On Mon, Feb 4, 2019 at 9:28 AM Alistair Grant wrote: > Hi Stef, > On Mon, 4 Feb 2019 at 09:20, ducasse wrote: > > > > Hi alistair > > > > >> HI alistair > > >> > > >> you should use the latest pillar. Was dev-7 and now it is 70 > > >> because this is around six months that we removed the

Re: [Pharo-dev] Debugger opening on user halt and not Object>>halt

Hi Thomas, Check the pragma debuggerCompleteToSender and its users. I think it's related to that. BenComan probably can give a better insight since (if I recall correctly) he introduced it? Guille On Wed, Jan 30, 2019 at 5:44 PM Thomas Dupriez wrote: > Hello, > > Does someone know which is

Re: [Pharo-dev] Contribute to pharo8.0 ?

Hi, there is an issue for this problem, https://github.com/pharo-project/pharo/issues/2379 We have identified the cause, I'll propose a fix now On Wed, Jan 30, 2019 at 8:44 AM ducasse wrote: > > > > There is currently a bug eating one character of the commit hash. So > > Iceberg does not

  1   2   3   4   5   6   7   8   >