March 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Smacc debugger

by Tudor Girba

They come with the ConfigurationOfSmaCC which is already in the Moose image. Doru > On Mar 27, 2017, at 4:52 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi > > where can I load the Smacc gt extension and debugger extensions? > > Stef -- www.tudorgirba.com www.feenk.com "Speaking louder won't make the point worthier."

March 27, 2017

Smacc question

by Stephane Ducasse

Hi john I'm learning smacc as a challenge :) I read a review the tutorial that we extracted form your doc. I have the following expression FunctionTypeName = 'function' TypeNameList ( 'internal' | 'external' | 'constant' | 'payable' )* ( 'returns' TypeNameList )? and I started to handle the 'internal'.... Now my grammar does not succeed to parse (self parser parseFunctionTypeNameOptions: 'internal payable') Attempt one: did not work =================== FunctionTypeNameOptions : {{}} | FunctionTypeNameOptions "internal" 'option' {{}} | FunctionTypeNameOptions "external" 'option' {{}} | FunctionTypeNameOptions "constant" 'option' {{}} | FunctionTypeNameOptions "payable" 'option' {{}} Attempt two: did not work =================== FunctionTypeNameOptions : | FunctTypeNameOptions ; FunctTypeNameOptions : FunctTypeNameOptions "internal" 'option' {{}} | FunctTypeNameOptions "external" 'option' {{}} | FunctTypeNameOptions "constant" 'option' {{}} | FunctTypeNameOptions "payable" 'option' {{}} ; Attempt three: did not work ===================== FunctionTypeNameOptions : | FunctTypeNameOptions ; FunctTypeNameOptions : FunctTypeNameOption 'option' | FunctTypeNameOptions FunctTypeNameOption 'option' ; FunctTypeNameOption : "internal" 'option' {{}} | "external" 'option' {{}} | "constant" 'option' {{}} | "payable" 'option' {{}} ; I studied the JavaParser and I do not get why my version does not work modifiers_opt : | modifiers ; modifiers : modifier 'modifier' | modifiers modifier 'modifier' ; modifier : "public" 'token' {{Modifier}} | "protected" 'token' {{Modifier}} | "private" 'token' {{Modifier}} | "static" 'token' {{Modifier}} ; Thanks in advance. I could have try to do it in petitParser but I want to have a real experience with Smacc. Stef

March 27, 2017

Smacc debugger

by Stephane Ducasse

Hi where can I load the Smacc gt extension and debugger extensions? Stef

March 27, 2017

Smalltalk jobs in Germany

by Stephane Ducasse

Hi guys Tomcat is looking for Smalltalkers in Germany. Contact them not me :) richard.v-lavante(a)tomcat.de christian.mann(a)tomcat.de Stef Actually now we are still looking for more Smalltalker again. Therefore today I turn to You and want to ask, it You know anybody, who has at least 2-3 Y. ST-experience (no matter which system) and wants to work for longer time in Germany, beginning in next 4-10 weeks. I thank You for Your help in advance and look forward to interesting news from You. Have a nice week! Viele GrÃ¼Ãe Best Regards Pozdravy Richard v. Lavante *Tomcat**Â®** GmbH **ITÂ·ConsultingÂ·Management* *Tomcat*Â® GmbH Flughafen Oberpfaffenhofen Friedrichshafener Str. 1 82205 Gilching Tel. +49-(0)8105-771801-0 Fax. +49-(0)89-849544 Mobil: +49-(0)172-9778982 Mail: richard.v-lavante(a)tomcat.de www.tomcat.de GeschÃ¤ftsfÃ¼hrer: Dipl.-Ing.(univ.) Richard von Lavante Firmensitz: D-82205 Gilching Register: MÃ¼nchen HRB 85435 *Tomcat*Â® ist eingetragenes Warenzeichen der *Tomcat*Â® GmbH

March 27, 2017

Re: [Pharo-users] using UFFI in non-crashing way

by phil＠highoctane.be

On Mon, Mar 27, 2017 at 1:01 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > > > On Mon, Mar 27, 2017 at 12:04 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> >> 2017-03-27 11:34 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: >> >>> Well, you can capture the signal, but the problem is not the signal >>> itself but what caused the problem. The most common case of segfaut is >>> memory corruption (and thus a program that tries to wrongly interpret wrong >>> addresses). If you already corrupted the memory doing something wrong, how >>> can you "fix it"? >> >> >> I think important case here is creating wrappers for new C libraries. >> Common mistake is passing wrong structures to foreign function. Then image >> crashes and you need restart it and recover code - big waste of time and >> losing smalltalk liveness. >> > > But then the problem is on "how to not lose your code", not in FFI... > Am spending my time restarting my image due to this. Very frustrating to recreate the setup etc. Havign a way to detect go back one frame would be very handy. Phil

March 27, 2017

Re: [Pharo-users] using UFFI in non-crashing way

by Guillermo Polito

On Mon, Mar 27, 2017 at 12:04 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2017-03-27 11:34 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > >> Well, you can capture the signal, but the problem is not the signal >> itself but what caused the problem. The most common case of segfaut is >> memory corruption (and thus a program that tries to wrongly interpret wrong >> addresses). If you already corrupted the memory doing something wrong, how >> can you "fix it"? > > > I think important case here is creating wrappers for new C libraries. > Common mistake is passing wrong structures to foreign function. Then image > crashes and you need restart it and recover code - big waste of time and > losing smalltalk liveness. > But then the problem is on "how to not lose your code", not in FFI...

March 27, 2017

Re: [Pharo-users] Creating Dates before/after Daylight Saving Time change

by werner kassens

Hi Sven, i completely agree my monday is not necessarily your monday, but my monday is my monday independently of when i initiate it. my monday (a few days ago) does _not begin at another utc because of a dst change in the meantime. this behaviour could result in additional problems, apart from Petrs, eg in a program that wants to calc the position of a star for a certain date & time. werner On 03/26/2017 10:14 PM, Sven Van Caekenberghe wrote: >> On 26 Mar 2017, at 21:56, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Did you check the Zn counterpart because I know that some parts are much better. >> But I do not have them at hand. > You mean ZTimestamp (but it is not a part of Zinc HTTP Components). > > https://github.com/svenvc/ztimestamp > > This is an UTC, second precision timestamp without TZ info, and a number of interesting tools. > > However, that won't solve the issue raised. Some people think of a date as an abstract calendar date, while for others its a concrete day (my Monday is not your Monday if we are in different time zones). > > I don't think there is only one solution, both roles are needed/useful. > > Note that STON serialises Dates as YYYY-MM-DD which is what you seem to want. > > The ZTimezone class knows about the exact transitions, but that still does not mean that no weird things happen at the transition point, au contraire ;-) > >> Stef >> >> On Sun, Mar 26, 2017 at 10:17 AM, Petr Fischer <petr.fischer(a)me.com> wrote: >> Hello, >> >> 1) when I create date on: 2017/03/20 (before Daylight Saving Time change) with this code: >> >> D1 := Date year: 2017 month: 3 day: 26. >> >> Date object is created with instvars: >> start: 2017-03-26T00:00:00+01:00 >> duration: 1:00:00:00 >> >> 2) when I create same Date instance with the same code on/after: 2017/03/26 (after Daylight Saving Time change): >> >> D2 := Date year: 2017 month: 3 day: 26. >> >> Date instance with this instvars returned: >> start: 2017-03-26T00:00:00+02:00 >> duration: 1:00:00:00 >> >> 3) D1 != D2 >> >> So, for example: persisted instance of date (Date year: 2017 month: 3 day: 26) created before DST change is not equal with date instance (Date year: 2017 month: 3 day: 26) created after DST change. >> DST change breaks equality of the same date :( >> >> Is it OK? >> >> Thanks! Petr Fischer >> >> > >

March 27, 2017

Re: [Pharo-users] using UFFI in non-crashing way

by Denis Kudriashov

2017-03-27 11:34 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Well, you can capture the signal, but the problem is not the signal itself > but what caused the problem. The most common case of segfaut is memory > corruption (and thus a program that tries to wrongly interpret wrong > addresses). If you already corrupted the memory doing something wrong, how > can you "fix it"? I think important case here is creating wrappers for new C libraries. Common mistake is passing wrong structures to foreign function. Then image crashes and you need restart it and recover code - big waste of time and losing smalltalk liveness.

March 27, 2017

Re: [Pharo-users] using UFFI in non-crashing way

by Guillermo Polito

On Sun, Mar 26, 2017 at 7:21 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > On Sun, Mar 26, 2017 at 05:45:04PM +0200, Esteban Lorenzano wrote: > > > > > On 26 Mar 2017, at 15:40, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > > > > Hi, > > > > > > is it possible to use UFFI and avoid crashing the image when the > called code segfaults? > > > > > > In other words, can I somehow wrap the call and throw in-image > Exception/Error on failure instead of the whole thing crashing? > > > > thatâs not possible, once you segfault, you segfault. > > Ah, ok. > Well, you can capture the signal, but the problem is not the signal itself but what caused the problem. The most common case of segfaut is memory corruption (and thus a program that tries to wrongly interpret wrong addresses). If you already corrupted the memory doing something wrong, how can you "fix it"? > > > > > > Or is the only way to do that have the called thing running as a > separate app (e.g. via OSSubProcess) and communicate via pipes or sockets? > > > > thatâs not done. > > no idea how much effort is required to implement, but I imagine is not > trivial. > > Nono, I didn't mean making UFFI calls via socket (although that would be > interesting), but rather making a C app that would make the calls, and that > would provide a socket interface. (Which is what I typically do with other > langs). > > Thanks, > Peter > >

March 27, 2017

Re: [Pharo-users] Installing Voyage ??

by Norbert Hartl

Thanks for the tip but I know that. I have full access to the voyage code. Without knowing the reason and context an issue is useless. Norbert > Am 26.03.2017 um 19:35 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > Add an issue in the Voyage github repo and do a pull request to push esteban > releasing a new version. > > > On Sun, Mar 26, 2017 at 1:15 PM, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > I get that same problem, too, every time I do "Software update". But never understood the rationale of dropping a database at this point. I think we should remove this line > > Norbert > > > Am 25.03.2017 um 22:04 schrieb Hilaire <hilaire(a)drgeo.eu <mailto:hilaire@drgeo.eu>>: > > > > ah yeah, I wrote an internal durty hack to get it rolling > > > > cleanUp: aRepository > > (aRepository isKindOf: Boolean) ifFalse: [ aRepository dropDatabase] > > > > > >> Le 25/03/2017 Ã 21:46, Hilaire a Ã©crit : > >> It occurs in Pharo5, likely not in Pharo4, or may be I fixed in my > >> image, I don't remember. > > > > -- > > Dr. Geo > > http://drgeo.eu <http://drgeo.eu/> > > > > > > >

March 27, 2017