Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

On Wed, 11 Jan 2017 12:48:43 +0100, Sven Van Caekenberghe wrote: OK, thanks, you are right; I was confused by the new filter option in senders, somehow I assumed the list was not longer (and I ignored the scroll bar) - weird./mail/ yes it happens to me a lot and it is

Re: [Pharo-dev] Setting a project with smtalltalkCI

I think the comma here: #categories : [ ''RenoirSt*'' ], is the offending one :) Esteban > On 13 Jan 2017, at 21:58, Gabriel Cotelli wrote: > > Hi! anyone with smalltalkCI experience? > > I'm trying to setup travis CI integration for one of my projects >

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

thanks a lot guille for your positive attitude. You give me the energy to continue when I'm sometimes tired. :) Hi all, Just wanted to share this: https://github.com/guillep/pharo-snapcraft It is basically the code to generate a snap package of the pharo-vm using snapcraft. Using this,

Re: [Pharo-dev] Strange DNU effect on Windows with Pastell

can you open a bug entry. I'm dreaming about a Object with far less funky methods. On Wed, 11 Jan 2017 09:55:06 +0100, Torsten Bergmann wrote: But why the hell would there be a Object>>#head ?! IMHO such general selectors at this level should not be used unless there is

Re: [Pharo-dev] Setting a project with smtalltalkCI

Thank you Esteban, that was the problem. I overlooked it like 5 times... On Fri, Jan 13, 2017 at 6:11 PM, Esteban Lorenzano wrote: > I think the comma here: > > #categories : [ ''RenoirSt*'' ], > > is the offending one :) > > Esteban > > On 13 Jan 2017, at 21:58,

Re: [Pharo-dev] FFICallback crashes windows spur i386 vm

On Fri, Jan 13, 2017 at 11:01:42AM -0800, Aliaksei Syrel wrote: > Hi Peter, > > Latest windows VMs produce crash dumps ;) Excellent! :) Peter > > Cheers, > Alex > > On 13 January 2017 at 10:57, Peter Uhnak wrote: > > > On Fri, Jan 13, 2017 at 10:27:27AM -0800, Aliaksei

Re: [Pharo-dev] FFICallback crashes windows spur i386 vm

UPD: Works using 497 windows vm: http://files.pharo.org/vm/pharo-spur32/win/497.zip. Something was changed recently... Cheers, Alex On 13 January 2017 at 11:20, Peter Uhnak wrote: > On Fri, Jan 13, 2017 at 11:01:42AM -0800, Aliaksei Syrel wrote: > > Hi Peter, > > > > Latest

[Pharo-dev] Setting a project with smtalltalkCI

Hi! anyone with smalltalkCI experience? I'm trying to setup travis CI integration for one of my projects ( https://github.com/ba-st/RenoirSt/tree/smalltalk_ci) and I'm getting a cryptic error on the builds: https://travis-ci.org/ba-st/RenoirSt/jobs/191751457 Any hints are welcome. Thanks,

Re: [Pharo-dev] FFICallback crashes windows spur i386 vm

UPD: Works with latest *Mac* VM http://files.pharo.org/vm/pharo-spur32/mac/pharo-mac-i386-201701130756-83c0ef1.zip Cheers, Alex On 13 January 2017 at 20:43, Aliaksei Syrel wrote: > UPD: > Works using 497 windows vm: http://files.pharo.org/vm/ > pharo-spur32/win/497.zip. >

Re: [Pharo-dev] FFICallback crashes windows spur i386 vm

Hi Peter, Latest windows VMs produce crash dumps ;) Cheers, Alex On 13 January 2017 at 10:57, Peter Uhnak wrote: > On Fri, Jan 13, 2017 at 10:27:27AM -0800, Aliaksei Syrel wrote: > > Hi > > > > The following code crashes windows spur32 VM without crash.dmp: > > (crashes not

Re: [Pharo-dev] FFICallback crashes windows spur i386 vm

On Fri, Jan 13, 2017 at 10:27:27AM -0800, Aliaksei Syrel wrote: > Hi > > The following code crashes windows spur32 VM without crash.dmp: > (crashes not only in case of int8, but ulong, int16/32 and so on...) I don't think that Windows produces crash dumps (or they are empty files), but maybe

[Pharo-dev] The 2017 Stack Overflow Developer Survey is Now Live

Arden Thomas reports "Questions 39 and 47 give us an opportunity to mention Smalltalk." http://stackoverflow.blog/2017/01/The-2017-Stack-Overflow-Developer-Survey-is-Now-Live/ -- View this message in context:

[Pharo-dev] FFICallback crashes windows spur i386 vm

Hi The following code crashes windows spur32 VM without crash.dmp: (crashes not only in case of int8, but ulong, int16/32 and so on...) Callback instantiation: createCallback >^ FFICallback > signature: #(int8 (int8)) > block: [ :value | value ] C function: int8_t

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

Hi Guille, Thanks very much for making this available. I'm trying to build the snap and am getting the following error: # snapcraft Loaded local plugin for pharo-build-plugin Skipping pull pharo-sources (already ran) Skipping pull pharo-vm (already ran) Preparing to build pharo-sources Building

Re: [Pharo-dev] FFICallback crashes windows spur i386 vm

Hi Aliaksei, > On Jan 13, 2017, at 10:27 AM, Aliaksei Syrel wrote: > > Hi > > The following code crashes windows spur32 VM without crash.dmp: > (crashes not only in case of int8, but ulong, int16/32 and so on...) > > Callback instantiation: > >> createCallback >>^

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

Hi, looking at the commands I see sudo snap install --dangerous --devmode pharo-vm_6.0_amd64.snap Does this mean that: 1. snap has to be already installed in the system 2. root priviledges are required for installing snaps The first requirement is eyebrow-raising (considering the install

Re: [Pharo-dev] problem with linux: missing

The reason is that the vm binary is 64bit but the interpreter is for 32bit images. Therefor the plugins are 32bit, too. If there will be a 64bit vm plus image the dependencies would go away. We are close to that but not there. Norbert > Am 12.01.2017 um 15:00 schrieb Nicolas Anquetil

Re: [Pharo-dev] Can anyone explain #asInteger for Strings?

Yes it is legacy, yes changing it will break things. Now, this is not such an easy topic. I agree that the example given goes way too far (as a general parser), but most parsers will allow junk at the end, as in '100euro'. Often good, sometimes bad. So it depends on the use case. Strict vs

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

+42 > On 13 Jan 2017, at 11:50, Guillermo Polito wrote: > > Hi all, > > Just wanted to share this: > > https://github.com/guillep/pharo-snapcraft > > > It is basically the code to generate a snap package of the pharo-vm

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

Thank you. I'll try it on several Fedora versions. Cheers -- Pavel 2017-01-13 11:50 GMT+01:00 Guillermo Polito : > Hi all, > > Just wanted to share this: > > https://github.com/guillep/pharo-snapcraft > > It is basically the code to generate a snap package of the

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

Nice 2017-01-13 12:00 GMT+01:00 Esteban Lorenzano : > +42 > > On 13 Jan 2017, at 11:50, Guillermo Polito > wrote: > > Hi all, > > Just wanted to share this: > > https://github.com/guillep/pharo-snapcraft > > It is basically the code to generate a

Re: [Pharo-dev] Can anyone explain #asInteger for Strings?

Ugly. And old, really old. I remember at one point in time there was a "squeezeNumberOutOfString" or something like that. Now, I'd like to fix this, because it just introduces noise and probably a lot of strange code. But the problem is not fixing it on itself, but checking all possible users

[Pharo-dev] [ANN] Snapcraft for Pharo

Hi all, Just wanted to share this: https://github.com/guillep/pharo-snapcraft It is basically the code to generate a snap package of the pharo-vm using snapcraft. Using this, the VM is generated and packaged with all dependencies. This should help in running pharo in different linux

Re: [Pharo-dev] Can anyone explain #asInteger for Strings?

> On 13 Jan 2017, at 13:15, p...@highoctane.be wrote: > > I guess Number class readFrom: stringOrStream is more up to date. But it still allows junk at the end, that may or may not be what you want (e.g. if you want to validate an input field). > Phil > > On Fri, Jan 13, 2017 at 11:02 AM,

Re: [Pharo-dev] Can anyone explain #asInteger for Strings?

I guess Number class readFrom: stringOrStream is more up to date. Phil On Fri, Jan 13, 2017 at 11:02 AM, Sven Van Caekenberghe wrote: > Yes it is legacy, yes changing it will break things. > > Now, this is not such an easy topic. I agree that the example given goes > way too far

Re: [Pharo-dev] Can anyone explain #asInteger for Strings?

On Fri, Jan 13, 2017 at 1:24 PM, Sven Van Caekenberghe wrote: > > > On 13 Jan 2017, at 13:15, p...@highoctane.be wrote: > > > > I guess Number class readFrom: stringOrStream is more up to date. > > But it still allows junk at the end, that may or may not be what you want > (e.g. if