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

FFICallback crashes windows spur i386 vm

by Aliaksei Syrel

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 test(int8_t(*function)(int8_t), int8_t value) { > return function(value); > } FFI call: primCall: aCallback int8: aNumber > ^ self ffiCall: #(int8 test(FFICallback aCallback, int8 aNumber)) Test case: test > self > assert: (self primCall: self createCallback int8: 0) > equals: 0 Windows 10. VM from today: http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201701130756-83c0… Image 60343: http://files.pharo.org/image/60/60343.zip P.S. what is the best place to report FFI / Alien issues? P.P.S Iceberg works Cheers, Alex

Jan. 13, 2017

The 2017 Stack Overflow Developer Survey is Now Live

by Richard Sargent

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-… -- View this message in context: http://forum.world.st/The-2017-Stack-Overflow-Developer-Survey-is-Now-Live-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 13, 2017

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

by phil＠highoctane.be

On Fri, Jan 13, 2017 at 1:24 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 13 Jan 2017, at 13:15, phil(a)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). > Then I'd do something like this: input := '123'. regex := '^[0-9]{3,7}$'. (input matchesRegex: regex) ifTrue: [ Number readFrom: input ] ifFalse: [ nil ] where regex is adjusted for what I need (number of digits etc). http://www.regextester.com/21 Phil > > > Phil > > > > On Fri, Jan 13, 2017 at 11:02 AM, Sven Van Caekenberghe <sven(a)stfx.eu> > 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 (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 lenient. > > > > Also, let's not add more methods to String, please. > > > > > On 13 Jan 2017, at 10:51, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > > > > > 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 relying on such strange behaviour. I bet > that fixing it naively could lead to break your image :). > > > > > > On Fri, Jan 13, 2017 at 4:05 AM, Richard Sargent <richard.sargent@ > gemtalksystems.com> wrote: > > > I've come across an implementation of #asInteger and #asSignedInteger > in > > > Pharo 3.0 that leaves me scratching my head. > > > > > > Can anyone explain why it was defined to answer what it does for > strings > > > that one would really not expect to parse as a number. > > > > > > 'abc-123-xyz-897' asSignedInteger > > > ===> -123 > > > > > > To my mind, the method that does this for the example string should > have an > > > intention revealing name like #spelunkIntegerFromString or some such. > > > > > > > > > Thanks, > > > Richard > > > > > > > > > > > > -- > > > View this message in context: http://forum.world.st/Can- > anyone-explain-asInteger-for-Strings-tp4929502.html > > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > > > > > > > > > > >

Jan. 13, 2017

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

by Peter Uhnak

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 instructions are more complex than for pharo-vm), and both first and second requirement makes me think this is not for end-user consumers, but for e.g. remote deployment or something like that. My use case is a system where I don't have root but I want to run pharo (e.g. school computers, customers), so I would like to know if this can help me in any way. (Right now I circumvent root with dynamic linking... but it's half-assed, and not really tested cross-distro). Thanks, Peter On Fri, Jan 13, 2017 at 11:50:23AM +0100, 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 using > snapcraft. Using this, the VM is generated and packaged with all > dependencies. This should help in running pharo in different linux > distributions. > > I invite you to check it, report problems and submit fixes. > > Cheers, > Guille

Jan. 13, 2017

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

by Sven Van Caekenberghe

> On 13 Jan 2017, at 13:15, phil(a)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, Sven Van Caekenberghe <sven(a)stfx.eu> 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 (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 lenient. > > Also, let's not add more methods to String, please. > > > On 13 Jan 2017, at 10:51, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > > 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 relying on such strange behaviour. I bet that fixing it naively could lead to break your image :). > > > > On Fri, Jan 13, 2017 at 4:05 AM, Richard Sargent <richard.sargent(a)gemtalksystems.com> wrote: > > I've come across an implementation of #asInteger and #asSignedInteger in > > Pharo 3.0 that leaves me scratching my head. > > > > Can anyone explain why it was defined to answer what it does for strings > > that one would really not expect to parse as a number. > > > > 'abc-123-xyz-897' asSignedInteger > > ===> -123 > > > > To my mind, the method that does this for the example string should have an > > intention revealing name like #spelunkIntegerFromString or some such. > > > > > > Thanks, > > Richard > > > > > > > > -- > > View this message in context: http://forum.world.st/Can-anyone-explain-asInteger-for-Strings-tp4929502.ht… > > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > > > > >

Jan. 13, 2017

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

by phil＠highoctane.be

I guess Number class readFrom: stringOrStream is more up to date. Phil On Fri, Jan 13, 2017 at 11:02 AM, Sven Van Caekenberghe <sven(a)stfx.eu> 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 (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 lenient. > > Also, let's not add more methods to String, please. > > > On 13 Jan 2017, at 10:51, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > > > 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 relying on such strange behaviour. I bet that > fixing it naively could lead to break your image :). > > > > On Fri, Jan 13, 2017 at 4:05 AM, Richard Sargent <richard.sargent@ > gemtalksystems.com> wrote: > > I've come across an implementation of #asInteger and #asSignedInteger in > > Pharo 3.0 that leaves me scratching my head. > > > > Can anyone explain why it was defined to answer what it does for strings > > that one would really not expect to parse as a number. > > > > 'abc-123-xyz-897' asSignedInteger > > ===> -123 > > > > To my mind, the method that does this for the example string should have > an > > intention revealing name like #spelunkIntegerFromString or some such. > > > > > > Thanks, > > Richard > > > > > > > > -- > > View this message in context: http://forum.world.st/Can- > anyone-explain-asInteger-for-Strings-tp4929502.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > > >

Jan. 13, 2017

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

by Denis Kudriashov

Nice 2017-01-13 12:00 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > +42 > > On 13 Jan 2017, at 11:50, Guillermo Polito <guillermopolito(a)gmail.com> > 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 using > snapcraft. Using this, the VM is generated and packaged with all > dependencies. This should help in running pharo in different linux > distributions. > > I invite you to check it, report problems and submit fixes. > > Cheers, > Guille > > >

Jan. 13, 2017

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

by Pavel Krivanek

Thank you. I'll try it on several Fedora versions. Cheers -- Pavel 2017-01-13 11:50 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > 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 > distributions. > > I invite you to check it, report problems and submit fixes. > > Cheers, > Guille >

Jan. 13, 2017

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

by Esteban Lorenzano

+42 > On 13 Jan 2017, at 11:50, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi all, > > Just wanted to share this: > > https://github.com/guillep/pharo-snapcraft <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 distributions. > > I invite you to check it, report problems and submit fixes. > > Cheers, > Guille

Jan. 13, 2017

[ANN] Snapcraft for Pharo

by 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 pharo-vm using snapcraft. Using this, the VM is generated and packaged with all dependencies. This should help in running pharo in different linux distributions. I invite you to check it, report problems and submit fixes. Cheers, Guille

Jan. 13, 2017