[Pharo-dev] Re: What, exactly, does `#=` mean?

The general expectations are that = should be an equivalence relation - reflexive (a = a) = true - symmetric (a = b) = (b = a) - transitive (a = b) & (b = c) ==> (a = c) https://en.wikipedia.org/wiki/Equivalence_relation Note that = is currently not an equivalence relation for Float, because of

Re: [Pharo-dev] Project of Interest => Jekyll + Dynamic processing integration + Git(hubs)Pages => pharo in the middle

Le jeu. 28 mai 2020 à 10:28, Cédrick Béler a écrit : > > I tried Jekyll and Gatsby.js, and albeit the latest is a mix of SSR > and SPA, I found some of their ideas in how to organize content to be > valuable, but I can't stand the tooling or the feeling of facing an > > > You know I always try

Re: [Pharo-dev] uFFI: What is the difference between FFIExternalObject and FFIOpaqueObject?

It's very important to name the types explicitely in order to avoid confusion See https://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2017-November/268059.html Le ven. 22 mai 2020 à 15:30, Esteban Lorenzano a écrit : > > > On 22 May 2020, at 15:25, Esteban Lorenzano wrote: > > > On 22

Re: [Pharo-dev] State of Pillar

I'd say have pillar wiki syntax supported by pandoc, this would be the most effective way to pdf, tex, word, html, whatever output... Le jeu. 26 mars 2020 à 00:28, Stephen Smith a écrit : > Hi all, due to the current state of the world I'm trying to spend some > time helping with the Pharo

Re: [Pharo-dev] Bug 18632 : Virtual Machine parameters need to be documented

arious Smalltalk memory models written by John > McIntosh but are those papers/posts/articles still relevant? > > In other words Eliot (and your VM wizard friends), the VM (aka GC and > memory model) do need some "documentation love" for "the average > Smalltalker&qu

Re: [Pharo-dev] Bug 18632 : Virtual Machine parameters need to be documented

Hi Benoit, for some reason (?), your email was marked as SPAM in gmail... There is a short description in primitiveVMParameter, which is found in generated code, for example: https://raw.githubusercontent.com/OpenSmalltalk/opensmalltalk-vm/Cog/src/vm/gcc3x-cointerp.c or VMMaker source code (you

Re: [Pharo-dev] about signal

For example, whether a Semaphore would queue waiting process by order of registration (thru a linked list for example) or by order of priority (thru a Heap for example), would completely change its behavior. So isn't that kind of implementation detail SUPER important, especially when hidden in VM?

Re: [Pharo-dev] Debugging GCC code generation

rules (C89 is 30 years ago, not exactly as new as we pretend), the restrict keyword, etc... Le mer. 11 déc. 2019 à 21:14, Eliot Miranda a écrit : > > > On Wed, Dec 11, 2019 at 12:03 PM Nicolas Cellier < > nicolas.cellier.aka.n...@gmail.com> wrote: > >> Yes, >> But

Re: [Pharo-dev] Debugging GCC code generation

meaningful warning > and the non-optimizated version of the function. > > And again as you said, the only thing to learn about all this is that > we should not write crappy code. > > On Wed, Dec 11, 2019 at 7:11 PM Nicolas Cellier > wrote: > > > > Of course, w

Re: [Pharo-dev] Debugging GCC code generation

Of course, when I say "your" code, it's the code you have shown, and probably "our" (VMMaker) code ;) Le mer. 11 déc. 2019 à 19:05, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> a écrit : > Hi Pablo (again), > no, not a bug. > > The problem i

Re: [Pharo-dev] Debugging GCC code generation

Hi Pablo (again), no, not a bug. The problem is in the source code. The compiler has the right to presume that your code is exempt of UB, because you cannot depend on UB (obviously). So it can eliminate all code which corresponds to UB. The compiler has the right to assume that a pointer to an

Re: [Pharo-dev] Debugging GCC code generation

Hi Pablo, pointer aliasing is considered UB indeed and accessing a pointer outside of allocated bounds also is UB the recommended way to perform a between one pointer type and another (reinterpret_cast) is to use memcpy, so it should be: long v; int i[sizeof(long)/sizeof(int)];

Re: [Pharo-dev] BlueInk removal

Why is there no deprecation for classes? The class definition can belong to a deprecated package. For more advanced feature, the deprected globals could belong to another dictionary, a bit like Undeclared... Le mer. 27 nov. 2019 à 21:31, ducasse a écrit : > Cyril > > there is no deprecation for

Re: [Pharo-dev] make github issues clearer?

Le lun. 4 nov. 2019 à 07:17, Hernán Morales Durand a écrit : > > This is more severe with the VM front. > > Hernán > > > Hi Hernan, could you ellaborate the problem you observe with the VM front?

Re: [Pharo-dev] make github issues clearer?

+1 for improving the issues. I call that the "checkbox attitude": Opening an issue is mandatory for a change to be merged? No problem, i open an issue (just a title), check the box, et voilà... That's applying the letter of the law rather than the spirit of the law. Either the law is bad (too

Re: [Pharo-dev] Seg Fault Pharo 7.0.3

> frame and attempts to scan code to link it. > > Our diagnosis is speculative; this is extremely hard to reproduce. > Typically in repeating a crashing run SIGIO may no longer be delivered at > the same point because any remote server has now woken up and delivers > results s

Re: [Pharo-dev] about threeWayCompareTo:

This comparison was part of MiscPrimitivePlugin. MiscPrimitivePlugin is a false good idea: Smalltalk fallback code = VMMaker (slang) source Unfortunately, this is an illusion because unlike the C source inclusions in ST/X we don't have dynamic slang compilation! The consequence is that source

Re: [Pharo-dev] about threeWayCompareTo:

This was WIP, don't know if it stalled... Le lun. 16 sept. 2019 à 08:52, ducasse a écrit : > I see > > threeWayCompareTo: aString > "Do a three-way comparison between the receiver and anotherObject, > returning > -1 if self < anotherObject > 0 if self = anotherObject >

Re: [Pharo-dev] I have a dream... or why I think that compatibility is an illusion and bring us to the past

Note that I also cared to handle ^ as binary selector for Opal Unfortunately the issue staled (for good or bad reasons, don't know...) https://pharo.fogbugz.com/f/cases/13078/Allow-upArrow-caret-as-a-binary-selector Le mer. 11 sept. 2019 à 21:21, Nicolas Cellier < nicolas.cellier.ak

Re: [Pharo-dev] I have a dream... or why I think that compatibility is an illusion and bring us to the past

> > > On 11 Sep 2019, at 19:48, Nicolas Cellier < > nicolas.cellier.aka.n...@gmail.com> wrote: > > Ah, and I forgot about your argumentation Stef: > > you cannot forbid binary selectors altogether because some are ugly > @@*+!!! (I thi

Re: [Pharo-dev] I have a dream... or why I think that compatibility is an illusion and bring us to the past

Ah, and I forgot about your argumentation Stef: you cannot forbid binary selectors altogether because some are ugly @@*+!!! (I think I read this one in Asterix le gaulois) for the same reasons that youCanNOtfOrBIDunaYSElectORSWIthletTersBECauSESoMeaREUgly Le mer. 11 sept. 2019 à 19:44, Nicolas

Re: [Pharo-dev] I have a dream... or why I think that compatibility is an illusion and bring us to the past

Le mer. 11 sept. 2019 à 10:40, Serge Stinckwich a écrit : > > > On Wed, Sep 11, 2019 at 2:14 AM Gabriel Cotelli > wrote: > >> Looks like Christmas season opened early this year :) >> >> Jokes aside, I'm in favor of changing some of the characters we use for >> binary selectors to allow it to be

Re: [Pharo-dev] Floating-point numbers with radix (non-decimal)?

uding #4 above). > > James > > On Sep 4, 2019, at 10:36 PM, ducasse wrote: > > Hi nicolas > > let us fix this :) > > why 15r1.2e1 is not working? > why 15r1.2e1 is not equals to 15r1.2E1? > why would we need a new syntax? > > Stef > > On 5 Sep 2019, at 00:19,

Re: [Pharo-dev] Floating-point numbers with radix (non-decimal)?

Once upon a time, only uppercase letters were accpeted as extra digits (in base > 10) for both int and float Then 15r1.2E1 was not 15r1.2e1, the later being = 15r12.E Then it was considered better to understand hexadecimal numbers with lowercase too... and alternate-base Float became ambiguous

Re: [Pharo-dev] [Pharo-users] SequenceableCollection>>#allButFirst: inconsistence across subclasses

Personnally I sometimes want to break the contracts because I know that I don't need them and can optimize some performance-critical operations. A good example is Fraction. The invariants are: numerator isInteger and: [denominator isInteger and: [ denominator strictlyPositive and:

Re: [Pharo-dev] FloatArray

| a := LapackSGEMatrix randNormal: #(1000 1000). b := LapackSGEMatrix randNormal: #(1000 1000). [a * b] timeToRun 19 Le mar. 21 mai 2019 à 10:05, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> a écrit : > Hi Serge, > this is good news, having tensor flow bindings is also a must! > I have thi

Re: [Pharo-dev] FloatArray

Le mar. 21 mai 2019 à 18:55, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> a écrit : > I have updated Smallapack to version 1.6.1 so as to accelerate sum. > > | a b c | > a := LapackSGEMatrix randNormal: #(1 1). > b := a as: FloatArray. > c := a asAbstractMa

Re: [Pharo-dev] FloatArray

rate fine. > > Again, thanks for your contribution. I know it is a lot of work and a > pretty large area to cover. Python/Numpy has armies of people working on > this. > > Jimmie > > > On 5/21/19 2:54 AM, Nicolas Cellier wrote: > > Hi Jimmie, > I didn't take time y

Re: [Pharo-dev] FloatArray

nd Numpy is not my favorite. But it isn't uncomfortable. >> >> So I gave up and went back to Numpy. >> >> Thanks. >> >> >> >> On 5/20/19 5:17 PM, Nicolas Cellier wrote: >> >> Hi Jimmie, >> effectively I did not subsribe... >> Havi

Re: [Pharo-dev] FloatArray

something wrong to cause such a >> tremendous slow down. >> >> Python and Numpy is not my favorite. But it isn't uncomfortable. >> >> So I gave up and went back to Numpy. >> >> Thanks. >> >> >> >> On 5/20/19 5:17 PM, Nicolas Cellier wr

Re: [Pharo-dev] FloatArray

t them... [w2 maxOf: [:each | each]] bench. '984 per second. 1.02 milliseconds per run.' Le dim. 19 mai 2019 à 14:58, Jimmie a écrit : > On 5/16/19 1:26 PM, Nicolas Cellier wrote:> Any feedback on this? > > Did someone tried to use Smallapack in Pharo? > > Jimmie? &g

Re: [Pharo-dev] FloatArray

Any feedback on this? Did someone tried to use Smallapack in Pharo? Jimmie? Le jeu. 25 avr. 2019 à 22:50, ducasse a écrit : > Thanks nicolas. > We will discuss this during the sprint tomorrow. > > > On 25 Apr 2019, at 22:43, Nicolas Cellier < > nicolas.cellier.aka.

Re: [Pharo-dev] How to convey that a message create a new instance

Le dim. 28 avr. 2019 à 08:43, ducasse a écrit : > Tx I’m doing the same. > Now may be we should revisit the API of color to at least convert the > method indicating side effect but lying > to convey that they are functional. > > beOpaque > -> asOpaque > > adjustBrightness: > > > may

Re: [Pharo-dev] How to convey that a message create a new instance

Le dim. 28 avr. 2019 à 04:57, Ben Coman a écrit : > > On Sat, Apr 27, 2019, 14:27 ducasse wrote: > >> > >> Hi > >> > >> I was looking at the API of Color and it is really confusing to me and > wrong > >> For example beOpaque > >> > >> beOpaque > >> "Set the transparency of the receiver

Re: [Pharo-dev] FloatArray

thrilled to be > able to stay with Pharo and not have to use Python/Numpy. :) > > Thanks. > > Jimmie > > > On 4/25/19 12:38 PM, Nicolas Cellier wrote: > > Hi Jimmie, > The Metacello Configuration is not ready for Pharo7. > I have succeeded in loading Sma

Re: [Pharo-dev] FloatArray

MessageAsTempNode > Compiler > MessageNode > > > I do not know how to proceed from there. Any help greatly appreciated. > > Thanks. > > Jimmie > > > On 4/24/19 12:20 AM, Nicolas Cellier wrote: > > Hi, > I recommand inquiring about Smallapack, the Smalltalk i

Re: [Pharo-dev] FloatArray

Hi, I recommand inquiring about Smallapack, the Smalltalk interface to LAPACK, on squeaksource.com or github. You'll get the speed of numpy. There is a Metacello configuration. I have not checked the port on current Pharo, but I can reactivate if there is some interest. Le mer. 24 avr. 2019 à

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

Good find! The fac tthat FT_Face is not thread-safe is documented https://www.freetype.org/freetype2/docs/reference/ft2-base_interface.html Le mer. 10 avr. 2019 à 15:39, teso...@gmail.com a écrit : > Hello, > > After checking the problem with Guille, we have the hypothesis of the > source of

Re: [Pharo-dev] About

gins/MiscPrimitivePlugin/MiscPrimitivePlugin.c > > I found the old one. > Did I look in the wrong place? > > Stef > > On 10 Apr 2019, at 13:46, ducasse wrote: > > Thanks nicolas so we can use them then. > > On 10 Apr 2019, at 11:59, Nicolas Cellier < > nicol

Re: [Pharo-dev] About

VMMaker.oscog-sk.2367 Author: sk Time: 19 April 2018, 12:02:35.661622 pm UUID: 0c2401e3-1450-4f73-8e81-958f50171595 Ancestors: VMMaker.oscog- nice.2366 ** new primitive to compare strings (slang + JIT) answers negative smi, 0 or positive smi (instead of 1, 2 or 3 in the MiscPlugin) * Slang

Re: [Pharo-dev] managing modification of class initialization methods

Le lun. 4 mars 2019 à 21:35, Eliot Miranda a écrit : > > > On Mon, Mar 4, 2019 at 8:26 AM Sven Van Caekenberghe wrote: > >> (1) the basic concepts are clear (and have been for a long time): >> >> - when a class initialize method is loaded, it is executed afterwards, if >> and only if the source

Re: [Pharo-dev] managing modification of class initialization methods

Hi Ben, It's probably time to revisit http://smallissimo.blogspot.com/2011/08/lazy-initialization-of-shared-variable.html?m=1 Le lun. 4 mars 2019 à 03:47, Ben Coman a écrit : > In relation to developing sample solutions for an Exercism exercise, the > following observation was made about class

Re: [Pharo-dev] [Vm-dev] VMMaker in Pharo [Was: Squeak and Tonel]

Hi Tudor, Retrieving author and timestamp from git history is doable. The question is whether it will be still possible to contribute thru MC or not. If it is metadataless MC, there's no point, it's unusable. I think that the minimal metadata we have to maintain is the last MC ancestor. This can

Re: [Pharo-dev] DeleteVisitor and symbolic links

+1, following links is insanely dangerous Le mer. 13 févr. 2019 à 20:59, Torsten Bergmann a écrit : > Sven wrote: > > Thanks, Alistair, for taking care of all this stuff. > > +1 > >

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

Le lun. 11 févr. 2019 à 08:45, Norbert Hartl a écrit : > > > > Am 11.02.2019 um 08:00 schrieb esteba...@gmail.com: > > > > Hello! > > > > This is my weekly ChangeLog, from 4 February 2019 to 10 February 2019. > > You can see it in a better format by going here: >

Re: [Pharo-dev] atRandom & integer agnosticism

Try it in Squeak and pick the relevant methods. Open a bug report and commit the fix. Of course, original authorship will somehow be spoiled, so be kind and cite them in commit message. Le lun. 11 févr. 2019 à 07:59, David Richards < david.i.richards@gmail.com> a écrit : > Hello community. >

Re: [Pharo-dev] Spotter shortcut reset

Oups, it seems that my mail client was lagging... Le dim. 3 févr. 2019 à 17:19, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> a écrit : > Ben, > The figures in the table are quite linear. > Duration * rate = constant. > > It's just that you want to plot 1/ durat

Re: [Pharo-dev] Spotter shortcut reset

Ben, The figures in the table are quite linear. Duration * rate = constant. It's just that you want to plot 1/ duration or 1/ rate if you don't want to see an hyperbole x×y=cte Le dim. 3 févr. 2019 à 12:17, ducasse a écrit : > Wouahh you are not playing :) > This is cool. > My network at

Re: [Pharo-dev] naming convention for pharo-vm/lib/pharo/* directory?

t3/pharo/bin/pharo-vm/pharo' > > > On 25 Jan 2019, at 18:25, Dale Henrichs < > dale.henri...@gemtalksystems.com> wrote: > > > > Thanks Nicolas, > > > > Is it as simple as pharo/*, or could there be multiple directories > created and I need to pick the ri

Re: [Pharo-dev] naming convention for pharo-vm/lib/pharo/* directory?

I'm afraid it also depends on the overly complex rules burried deep inside the VM... It would be a good thing to try and document it. And if we can't reasonably document it, then we might want to open an issue on opensmalltalk. Le ven. 25 janv. 2019 à 01:51, Dale Henrichs <

Re: [Pharo-dev] DebugSession>>activePC:

Le ven. 18 janv. 2019 à 14:42, Marcus Denker a écrit : > > > > On 18 Jan 2019, at 14:26, ducasse wrote: > > > > I simply love the dynamic rewriting this is just too cool. We should > systematically use it. > > I will continue to use it in any deprecation. > > > > On my TODO is to make it

Re: [Pharo-dev] [Vm-dev] Better management of encoding of environment variables

n many places > I don't recommend it. > > PS: oups, sorry for out of band message, I wanted to send, but it seems > that I did not press the button properly... > >> >>> > On 16 Jan 2019, at 10:59, Guillermo Polito >>> wrote: >>> > >>> &g

Re: [Pharo-dev] [Vm-dev] Better management of encoding of environment variables

riants (thus potentially lot of code) - complexity tends to spread in many places I don't recommend it. PS: oups, sorry for out of band message, I wanted to send, but it seems that I did not press the button properly... > >> > On 16 Jan 2019, at 10:59, Guillermo Polito >> wrote: >> &

Re: [Pharo-dev] Purpose of VM [was: Re: Better management of encoding of environment variables]

. But if a full rewrite is wanted for other reasons, no problem. Le jeu. 17 janv. 2019 à 02:00, Martin McClure a écrit : > On 1/16/19 1:24 AM, Nicolas Cellier wrote: > > IMO, windows VM (and plugins) should do the UCS2 -> UTF8 conversion > > because the purpose of a VM is to provide an OS

Re: [Pharo-dev] Better management of encoding of environment variables

IMO, windows VM (and plugins) should do the UCS2 -> UTF8 conversion because the purpose of a VM is to provide an OS independant façade. I made progress recently in this area, but we should finish the job/test/consolidate. If someone bypass the VM and use direct windows API thru FFI, then he takes

Re: [Pharo-dev] Availability of Smallapack in Pharo6.0

Le sam. 12 janv. 2019 à 14:14, Denis Kudriashov a écrit : > Hi Nicolas > > пт, 11 янв. 2019 г. в 23:34, Nicolas Cellier < > nicolas.cellier.aka.n...@gmail.com>: > >> Hi, >> I announce the availability of Smallapack in Pharo6. >> >>

Re: [Pharo-dev] Shortcut for programmatically executing a class side method ?

Normally, primitive 188 and 189 execute a method (the receiver is the method receiver). Maybe search for senders... Le dim. 13 janv. 2019 à 22:42, Sven Van Caekenberghe a écrit : > Hi, > > Does there exist a shortcut for programmatically executing a class side > method ? > > For example, > >

Re: [Pharo-dev] Development process: testing the GUI

> > > On 12 Jan 2019, at 23:34, Nicolas Cellier < > nicolas.cellier.aka.n...@gmail.com> wrote: > > Hi all, > Pharo team is attaching great care in securing and improving the > development process, notably by promoting usage of tests and continuous > integratio

[Pharo-dev] Development process: testing the GUI

Hi all, Pharo team is attaching great care in securing and improving the development process, notably by promoting usage of tests and continuous integration. I think a very good job is already done in the libraries provided by Pharo. But sometimes I encounter more hickups with the development

[Pharo-dev] Availability of Smallapack in Pharo6.0

Hi, I announce the availability of Smallapack in Pharo6. The ConfigurationOfSmallapack is in http://www.squeaksource.com/MetacelloRepository and there is a copy in meta repo for Pharo 3/4/5/6. Currently, the ported version uses a derivative of OpalCompiler patched to handle method with 16+

Re: [Pharo-dev] Is metacello aware of MC branches???

the baseline you can have: > > spec package: 'Smallapack-StdLib' with: [ > spec > file: 'Smallapack-StdLib.UFFI-nice'] > ] > > > Cheers, > Andrei > > > On Fri, Jan 11, 2019 at 12:19 PM Nicolas Cellier < > nicolas.cellier.aka.n...@g

[Pharo-dev] Is metacello aware of MC branches???

Hi all, I'm trying to resolve a dialect compatibility problem like this: I want to load the Squeak and Pharo3 to 5 version depending on FFI Smallapack-StdLib-nice.1 For Pharo6, I made a different branch depending on UFFI Smallapack-StdLib.UFFI-nice.1 In the base line, i tell spec for:

[Pharo-dev] FFILibrary uniqueInstance

Hi all, I wanted to know if the moduleName was cached somewhere or recomputed at each function call... It seems to be recomputed. We could have a different scheme: moduleName is cached in a class inst var of FFILibrary. FFILibrary is then added to startup list and moduleName is reset when

Re: [Pharo-dev] [Issue 19852] Cached settings and moving images

Le mar. 8 janv. 2019 à 17:36, Guillermo Polito a écrit : > Hi Eliot, > > Thanks for looking into this, see inline. > > On Tue, Jan 8, 2019 at 4:46 PM Eliot Miranda > wrote: > >> Hi Guille, >> >> On Jan 8, 2019, at 3:19 AM, Guillermo Polito >> wrote: >> >> Hi all, >> >> I was checking issue

Re: [Pharo-dev] libssh2 1.7.0 & 1.8.0

At the risk of being pedantic, if we were really serious, for mid term, it would be good to not compile ssl, but just link. https://www.cvedetails.com/vulnerability-list/vendor_id-217/product_id-383/opdos-1/Openssl-Openssl.html Le ven. 4 janv. 2019 à 10:13, Alistair Grant a écrit : > Hi

Re: [Pharo-dev] [Vm-dev] LibC system pops up a CMD.exe window in Windows 10 (Pharo 6.1)

attached to it. >> >> Guille >> >> On Wed, Dec 12, 2018 at 12:30 AM Eliot Miranda >> wrote: >> >>> >>> Hi Nicolas, >>> >>> On Tue, Dec 11, 2018 at 5:43 AM Nicolas Cellier < >>> nicolas.cellier.aka.n...@gmail.com>

Re: [Pharo-dev] LibC system pops up a CMD.exe window in Windows 10 (Pharo 6.1)

It is possible, ask stack overflow https://stackoverflow.com/questions/4743559/how-to-execute-child-console-programs-without-showing-the-console-window-from-th https://stackoverflow.com/questions/18841971/hide-console-window-while-running-a-command-through-c?r=SearchResults I've recently "fixed"

Re: [Pharo-dev] Minheadless trial

Hi Esteban, Ronie, Forking, branching and merging is certainly the clean way to do it! The question is about the frequency of merges. Like Ben I prefer short cycles, because otherwise we just can't review the code, it' too many diffs at once. We can just trust, or not, take it or leave it... So

Re: [Pharo-dev] Cannot use Zinc in Pharo7 anymore

So the killer feature is not the possibility to report issues, propose and link corrections, enhancements and new features to be merged back, have them automatically tested on continuous integration bots, comment code online and have discussions about implementation correctness or style... If

Re: [Pharo-dev] [Pharo-users] [ANN] Success story Mobility Map

Hi Norbert, Le lun. 1 oct. 2018 à 19:22, Norbert Hartl a écrit : > > > Am 26.09.2018 um 19:22 schrieb Nicolas Cellier < > nicolas.cellier.aka.n...@gmail.com>: > > Very nice proof that we can leverage efficient and up to date technologies > ! > > > That was

Re: [Pharo-dev] [Pharo-users] [ANN] Success story Mobility Map

Very nice proof that we can leverage efficient and up to date technologies ! Thank you so much for sharing, that's the right way to make Pharo (and Smalltalk) alive and kicking. How did the Pharo IDE help in such context? (did you use debugging facility extensively?). What tool is missing? Le

Re: [Pharo-dev] [rmod] Float should not implement #to:, #to:by:, etc...

Hi Davide, Using decimals is a possibility which already exists, just add a $s at end of the literal. What you suggest is to change the syntax and use decimal as the default, and another notation (or no literal notation at all, just asFloat message send) for floating point numbers. It's worth

Re: [Pharo-dev] [rmod] Float should not implement #to:, #to:by:, etc...

Le mar. 18 sept. 2018 à 22:40, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> a écrit : > > > Le mar. 18 sept. 2018 à 11:53, Guillaume Larcheveque < > guillaume.larcheve...@gmail.com> a écrit : > >> Maybe #to:by: should convert its parameters in Fra

Re: [Pharo-dev] [rmod] Float should not implement #to:, #to:by:, etc...

Le mar. 18 sept. 2018 à 11:53, Guillaume Larcheveque < guillaume.larcheve...@gmail.com> a écrit : > Maybe #to:by: should convert its parameters in Fraction to avoid Floats > problems (not sure, just an idea) > > Hi Guillaume, Yes possibly... But if the author explicitely requested a loop on

Re: [Pharo-dev] [rmod] Float should not implement #to:, #to:by:, etc...

Hi Julien, You are right, Float intervals are not to be encouraged! But if a knowledgeable person wants to use it, why forbid it? Why not forbid Float alltogether then? In the same vein, I saw C compiler warning me about using Float = (== in C). Great! Now I cannot use -Wall -Werror, though I

Re: [Pharo-dev] Esteban's ChangeLog week of 23 July 2018

Hi Esteban, I encountered this problem a few months ago. I tried to document FFI with a serie of stackoverflow questions https://stackoverflow.com/questions/49783882/how-one-deals-with-typedefs-in-squeak-ffi

Re: [Pharo-dev] Problem with zinc 2.9.2

Isn't there a recent PR on opensmalltalk that address just this? Le jeu. 12 juil. 2018 à 23:16, Max Leske a écrit : > Hi Norbert, > > I was able to reproduce the problem and then identify the culprit, > although what I don't yet understand is how this is related to the changes > in Zinc. > >

Re: [Pharo-dev] Hash on collections

2018-06-21 0:16 GMT+02:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > > > 2018-06-21 0:00 GMT+02:00 : > >> >> >> >> >> *From:* Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] *On Behalf >> Of *Nicolas Cellier >> *Sent

Re: [Pharo-dev] Hash on collections

2018-06-21 0:00 GMT+02:00 : > > > > > *From:* Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] *On Behalf > Of *Nicolas Cellier > *Sent:* Wednesday, June 20, 2018 14:52 > *To:* Pharo Development List > *Subject:* Re: [Pharo-dev] Hash on collections > > > &

Re: [Pharo-dev] Empirical Analysis of Programming Language Adoption

2018-06-08 17:05 GMT+02:00 Thierry Goubier : > 2018-06-08 16:35 GMT+02:00 Nicolas Cellier gmail.com>: > > > > > > 2018-06-08 14:50 GMT+02:00 Thierry Goubier : > >> > >> Hi Ben, > >> > >> Interesting find. > >> > >>

Re: [Pharo-dev] Empirical Analysis of Programming Language Adoption

2018-06-08 17:06 GMT+02:00 Thomas Dupriez < thomas.dupr...@ens-paris-saclay.fr>: > Hello, > I wanted to just write a quick comment, but it turned into an essay, > sorry. ^^ > > Le 08/06/2018 à 16:35, Nicolas Cellier a écrit : > > > > 2018-06-08 14:50 GMT+02:

Re: [Pharo-dev] Empirical Analysis of Programming Language Adoption

2018-06-08 14:50 GMT+02:00 Thierry Goubier : > Hi Ben, > > Interesting find. > > ... snip ... > > > Table 7 makes and interesting assertion that static types are more > important > > for readability than preventing bugs. > > This one is in line with Dan Luu meta-study that static typing catches >

Re: [Pharo-dev] Horrible mess in keyboard modifiers processing

2018-05-29 9:58 GMT+02:00 Guillermo Polito : > He, i think this may be a VM issue. I've fixed part of the keyboard event > handling in the past, but it's effectively a mess... > Yes, there are some issues opened already

Re: [Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

2018-05-14 15:15 GMT+02:00 Marcus Denker <marcus.den...@inria.fr>: > > > On 14 May 2018, at 15:09, Nicolas Cellier <nicolas.cellier.aka.nice@ > gmail.com> wrote: > > > > 2018-05-14 14:44 GMT+02:00 Marcus Denker <marcus.den...@inria.fr>: > >>

Re: [Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

2018-05-14 14:44 GMT+02:00 Marcus Denker : > > > > > > For ByteArray, I didn't check recently in Pharo, but I know that it's > quite a mess in Squeak because some methods are in Alien, other in FFI, > other in base Squeak... > > IMO all methods should be in core

Re: [Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

2018-05-14 13:22 GMT+02:00 Guillermo Polito : > > > On Fri, Apr 20, 2018 at 5:24 PM, Sven Van Caekenberghe > wrote: > >> Hi, >> >> After the File and Stream changes in Pharo 7, a binary read, resp. write >> stream from/to a file is actually a

Re: [Pharo-dev] Pharo Bootstrap familiarity

Nice reverse engineering! MOP is Meta Object Protocol (serach in reference [9]). Maybe you miss a reference to the definition of BaselineOfPharoBootstrap

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

2018-04-11 19:08 GMT+02:00 Alistair Grant : > Hi Sven, > > On 11 April 2018 at 18:53, Sven Van Caekenberghe wrote: > > Something is off (and/or I am getting crazy, probably both). > > > > $ ./pharo --headless Pharo.image eval '(FileStream stdin binary; next:

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

Hi Alistair, I must take my part too: I suggested that we could use a pair of getc/ungetc to know if we are atEnd(OfData), but this obviously works well with AsyncFileIO only, else it blocks. For files, this generally isn't a problem (but maybe for network mounted partitions), the latency is

Re: [Pharo-dev] Images, VMs and 32 vs 64bit

The general principle is that the VM insulate almost every OS specific feature: the image sees the same virtual machine. So you can save a 32bits image on an OS, and restart it on another. The images effectively share the same code base whatever the OS. There might be a plugin or two which are not

Re: [Pharo-dev] Idea and proof of concept: Accept for Test

Yes this is cool. I was wondering what if you try and modify the Meta-Link architecture itself, but my brain did not reach this second meta level... 2018-04-04 21:50 GMT+02:00 Sven Van Caekenberghe : > Very cool. Impressive combination of unique Pharo features. > > > On 4 Apr 2018,

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

2018-04-04 12:18 GMT+02:00 Alistair Grant : > Hi Sven, > > On Wed, Apr 04, 2018 at 11:32:02AM +0200, Sven Van Caekenberghe wrote: > > Somehow, somewhere there was a change to the implementation of the > > primitive called by some streams' #atEnd. > > That's a proposed

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

Hi Sven, See also discussion at https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/232 2018-04-04 11:32 GMT+02:00 Sven Van Caekenberghe : > Somehow, somewhere there was a change to the implementation of the > primitive called by some streams' #atEnd. > > IIRC, someone said it

Re: [Pharo-dev] AnnouncementSubscription and Ephemerons

2018-04-01 11:36 GMT+02:00 Stephane Ducasse : > Hi Torsten > > Thanks for this question. > > Ephemerons do not work in Pharo sadly and we know it. We cannot then > take advantage of them. > What you see is in fact a degradation of the situation around the VM. :( > We are

Re: [Pharo-dev] Writing into stream from another stream

There are two different questions: - expressiveness - efficiency Real efficiency of transfer (without any intermediate copy) is only guaranteed in very rare cases (if the target collection of write stream is same species as source collection of read stream, and there are no transform in any of

Re: [Pharo-dev] New Files in Pharo - Migration Guide, How To's and examples

2018-03-19 21:21 GMT+01:00 Denis Kudriashov : > > > 2018-03-19 20:39 GMT+01:00 Esteban A. Maringolo : > >> 2018-03-19 16:32 GMT-03:00 Denis Kudriashov : >> > >> > Hi Guille. >> >> > What you think to add helpfull converting

Re: [Pharo-dev] Executive Summary of the recent FileStream Changes

Very good initiative! It's worth a few hick-ups. I've tried to reduce RWBinaryOrTextStream usage in Squeak maybe 10 years ago, but you know it very well, the last places which are resisting are the more intricated and convoluted. I call it the SwiisKnifeStream and allways wandered why we would

Re: [Pharo-dev] FileSystem tweaks (was Re: new pharo cheatsheet)

2018-03-08 19:44 GMT+01:00 Eliot Miranda : > Hi Sven, > > On Mar 8, 2018, at 9:55 AM, Sven Van Caekenberghe wrote: > > > > On 8 Mar 2018, at 17:58, Eliot Miranda wrote: > > > Hi Stef, > > > following on from Sean, (+1000 for using

Re: [Pharo-dev] Released versions in Pharo Bootstrap

2018-03-05 18:23 GMT+01:00 Stephan Eggermont : > Guillermo Polito > wrote: > >... > > > > So yes, it may block upgrades, but until we have tools that allow us to > > cope with the complexity, I prefer to have reproducible versions where I > > can

Re: [Pharo-dev] Released versions in Pharo Bootstrap

The well known problem with fixed configurations is dependencies: My project A version 1.2.3 depends on project C version 4.3 (semantic versioning). I have tested it with 4.3.35, it works well... If semantic versioning is correctly used, it should work with any 4.x.y where x>=3. There is another

  1   2   3   4   5   6   >