January 2019 - Pharo-users - lists.pharo.org

Porting Github packages to Pharo 7

by HernÃ¡n Morales Durand

I would like your advice on this: What's the effortless way to migrate Github repository from Pharo 6 to Pharo 7? I thought in the following solutions: 1) In a Pharo 6 image modify my BaselineOf, add & push a new package MyPackage-Pharo6, then load it into a Pharo 7 image, create MyPackage-Pharo7 and port as needed. The same Metacello installation script is preserved for all versions. 2) Tag repository as x.x in a Pharo 6 image, load my package & do port in a Pharo 7 image and push to master. Previous Pharo 6 version could be loaded referring to a tag (or branch maybe?) in the Metacello installation script. Any recommendations? Alternative paths? Cheers, HernÃ¡n

Jan. 31, 2019

Re: [Pharo-users] Fwd: startup error in windows 10

by Benoit St-Jean

Hi Hilaire, Unfortunately, Dr. Geo suffers from the same problem I have with any Pharo 6.x and 7.x image regarding the encoding of my name in Windows.Â It crashes when the app starts at the exact same place and I can't do much.Â Sorry. On 2019-01-30 08:15, Hilaire wrote: > Hi Benoit, > > It is DrGeo 18.06 > https://launchpad.net/drgeo/trunk/18.06/+download/DrGeo.app-18.06a.zip > > Thanks to try out. > > Hilaire > > Le 30/01/2019 Ã 00:16, Benoit St-Jean via Pharo-users a Ã©critÂ : >> Hilaire, do you have an URL so I can download the exact same thing >> that users has?Â I'm also on Windows 10. >> >> I'll try to run in dev mode and see what happens! -- ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero". (A. Einstein)

Jan. 31, 2019

Re: [Pharo-users] Fwd: startup error in windows 10

by Ben Coman

On Wed, 30 Jan 2019 at 03:28, Hilaire <hilaire(a)drgeo.eu> wrote: > I asked the user to send me the PharoDebug.log to have a more accurate > feedback: > > http://forum.drgeo.eu/file/n4025537/PharoDebug.log > > Of course I should make him to test with a newer VM to see if the > problem is gone, but it is a bit more complicate. > > Are the video info necessary? The image world starts just fine. > Maybe not critical. Just trying to get coverage. If two people download the same binary and get different results, then its something different in the environment and a matter of carving up that space looking for patterns. I've seen graphics issues arising only on specific video cards before. cheers -ben > > Hilaire > > Le 28/01/2019 Ã 23:34, Ben Coman a Ã©crit : > > To provide the best chance for someone to help, can you provide: > > * base Image version > > * vm version > > * systeminfo.exe (stripped of personally identifying data) > > * with dates added to hotfixes from > > ( > https://www.tenforums.com/tutorials/5472-view-windows-update-history-window… > ) > > * video info from (wmic path win32_VideoController get /all > > /format:htable >> c:\temp\graphics.html) > > -- > Dr. Geo > http://drgeo.eu > > > >

Jan. 31, 2019

Re: [Pharo-users] SmaCC parsing "rest until"

by Manuel Leuenberger

Hi Thierry, Thanks for the ideas and references. I also tried parsing with PetitParser2, because with PEGs I can have unlimited lookahead. Still, I did not get it working quickly, and it was ugly anyway. One way would also be to just tokenize the whole remainder of the line into words, and rebuild the rest without the last word in a second step. Ultimately, it was easier to write a hand-knitted parser that does exactly that (https://github.com/maenu/leak-reporter/blob/master/src/pharo/LeakReporter/L… <https://github.com/maenu/leak-reporter/blob/master/src/pharo/LeakReporter/L…>), the structure is easy enough. Cheers, Manuel > On 30 Jan 2019, at 19:19, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 29/01/2019 Ã 22:17, Manuel Leuenberger a Ã©crit : >> Hi, >> I am currently struggling with understanding why my SmaCC parser refuses to parse a rather simple language. Grammar and example are below. >> The language consists of multiple leak reports, separated by two newlines. Each leak report has a type and object and byte size on the first line. Then comes a stack of indented frames with addresses, and method and source location if available. Somehow my parser always fails because it trying to scan the whole string as <method>. I am struggling with this since hours but not making any progress. >> How do I need to rewrite the grammar so that the scanner produces the right tokens for the parser? >> I understand that the <method> token use in Source is problematic, because it needs to match until the last word. But I cannot find a way to write it in another way or tweak the parser attributes to figure out the right tokenization. > > Hi Manuel, > > the problem is effectively your <method> tag, which is eating next to everything. > > In such a situation, you could use a state in your scanner, limit <method> to that state, and switch in and out of that state in the parser actions. > > something like: > > inMethod <method> : ; > > in: "in" {self state: #inMethod}; > > method: <method> {self state: #default}; > > See section 3.6 in the SmaCC booklet. > >> Anybody has some hints? I would greatly appreciate it. > > The scanner state may help, but I think your <method> tag has to be better defined, else you will be unable to get the <file> part. > > Source > : " (<unknown module>)" { #unknown } > | "in " <method> 'method' " " <file> 'file' { { method value . file value } } > ; > > Avoid having spaces into the terminals (i.e. "in "), and it won't probably match the " ". > > What I can only suggest is to write a <method> (or method non terminal) closed by a space, and only allowing spaces if inside enclosing parenthesis "(" ")" or brackets "<" ">"; what is after the space is the <file>. > > Hope this helps, > > Thierry > >> Cheers, >> Manuel >> Example: >> LeReParser parse: 'Indirect leak of 8 byte(s) in 1 object(s) allocated from: >> #0 0x106be248c in wrap_malloc (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x5d48c) >> #1 0x12193989d in moz_xmalloc mozalloc.cpp:83 >> #2 0x11fc8200d in std::__1::vector<unsigned int, std::__1::allocator<unsigned int> >::__append(unsigned long) mozalloc.h:194 >> #3 0x11fc80d5a in mozilla::gfx::GradientStopsSkia::GradientStopsSkia(std::__1::vector<mozilla::gfx::GradientStop, std::__1::allocator<mozilla::gfx::GradientStop> > const&, unsigned int, mozilla::gfx::ExtendMode) vector:2041 >> #4 0x11fc6f1dc in mozilla::gfx::DrawTargetSkia::CreateGradientStops(mozilla::gfx::GradientStop*, unsigned int, mozilla::gfx::ExtendMode) const DrawTargetSkia.cpp:62 >> #5 0x122236b1e in create_gradient_stops(mozilla::gfx::DrawTarget*, float*, unsigned int, mozilla::gfx::ExtendMode) pattern.cpp:98 >> #6 0x122236323 in moz2d_pattern_linear_gradient_create_flat pattern.cpp:40 >> #7 0x1069cf901 in primitiveCalloutWithArgs (Pharo:x86_64+0x1003a5901) >> #8 0x10669e222 in primitiveExternalCall gcc3x-cointerp.c:76887 >> #9 0x106694aed in executeNewMethod gcc3x-cointerp.c:22341 >> #10 0x10669a403 in ceSendsupertonumArgs gcc3x-cointerp.c:16540 >> #11 0x11043c134 (<unknown module>) >> #12 0x10662d712 in interpret gcc3x-cointerp.c:2754 >> #13 0x1068b2ada in -[sqSqueakMainApplication runSqueak] sqSqueakMainApplication.m:201 >> #14 0x7fffc93786fc in __NSFirePerformWithOrder (Foundation:x86_64+0xd76fc) >> #15 0x7fffc78cfc56 in __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ (CoreFoundation:x86_64h+0xa6c56) >> #16 0x7fffc78cfbc6 in __CFRunLoopDoObservers (CoreFoundation:x86_64h+0xa6bc6) >> #17 0x7fffc78b05f8 in __CFRunLoopRun (CoreFoundation:x86_64h+0x875f8) >> #18 0x7fffc78b0033 in CFRunLoopRunSpecific (CoreFoundation:x86_64h+0x87033) >> #19 0x7fffc6e10ebb in RunCurrentEventLoopInMode (HIToolbox:x86_64+0x30ebb) >> #20 0x7fffc6e10bf8 in ReceiveNextEventCommon (HIToolbox:x86_64+0x30bf8) >> #21 0x7fffc6e10b25 in _BlockUntilNextEventMatchingListInModeWithFilter (HIToolbox:x86_64+0x30b25) >> #22 0x7fffc53a5a53 in _DPSNextEvent (AppKit:x86_64+0x46a53) >> #23 0x7fffc5b217ed in -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] (AppKit:x86_64+0x7c27ed) >> #24 0x7fffc539a3da in -[NSApplication run] (AppKit:x86_64+0x3b3da) >> #25 0x7fffc5364e0d in NSApplicationMain (AppKit:x86_64+0x5e0d) >> #26 0x7fffdd0a2234 in start (libdyld.dylib:x86_64+0x5234) >> '. >> Grammar: >> %prefix LeRe; >> %suffix Node; >> %root Report; >> <newline> >> : \r \n? | \n >> ; >> <number> >> : \d+ >> ; >> <index> >> : \# \d+ >> ; >> <address> >> : 0 x [0-9a-f]+ >> ; >> <method> >> : [^\r\n]+ >> ; >> <file> >> : \S+ >> ; >> Report >> : Leaks 'leaks' { leaks } >> ; >> Leaks >> : Leak 'leak' { { leak } } >> | Leaks 'leaks' Leak 'leak' { leaks , { leak } } >> ; >> Leak >> : LeakType 'type' <number> 'bytes' " byte(s) in " <number> 'objects' " object(s) allocated from:" <newline> Stack 'stack' <newline> { { type . bytes value . objects value . stack } } >> ; >> LeakType >> : "Indirect leak of " { #indirect } >> | "Direct leak of " { #direct } >> ; >> Stack >> : Frames 'frames' { frames } >> ; >> Frames >> : Frame 'frame' { { frame } } >> | Frames 'frames' Frame 'frame' { frames , { frame } } >> ; >> Frame >> : " " <index> " " <address> " " Source 'source' <newline> { source } >> ; >> Source >> : " (<unknown module>)" { #unknown } >> | "in " <method> 'method' " " <file> 'file' { { method value . file value } } >> ; >

Jan. 30, 2019

Re: [Pharo-users] [ANN] Pharo open documentation

by Julien

Hello Offray, Not really, awesome lists are not gathering documentation. These lists are about creating an index of links to cool projects working in Pharo. The wiki is for documenting parts of the system and provide useful code snippets. But maybe a Â« main page Â» in a Â« meta repository Â» should hold pointers to all the repositories of Pharo open documentation organisation. It might be a good idea. :-) Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > Le 30 janv. 2019 Ã 17:51, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> a Ã©crit : > > Hi Cyril, > > Thanks for your work on this. > > Just to clarify, the Pharo Wiki is the entry points for all the other > documentation projects? If that's the case, should be expected that the > Awesome Pharo and Awesome Pharo ML are linked there? > > Cheers, > > Offray > > On 30/1/19 9:00, Cyril Ferlicot wrote: >> Hi everyone! >> >> With some other members of the community we are proud to announce a >> new effort on Pharo documentation. >> >> We launched an organization pharo-open-documentation which is a >> user-maintained documentation related to Pharo environment, language, >> and libraries. >> >> Currently it has three main projects: >> - pharo-wiki : Wiki related to the Pharo programming language and environment. >> - awesome-pharo : A collection of awesome Pharo libraries, tools, >> frameworks and software. We want to make this project a reference in >> https://github.com/sindresorhus/awesome >> - awesome-pharo-ml : List of projects, books, booklets, papers, and >> applications related to machine learning, AI, data science in Pharo. >> >> Contributions are welcomed! >> >> If you own a cool project in Pharo others could use in their own >> projects, send us a PR to awesome-pharo! >> If you have knowledge on Pharo or projects of Pharo, we would be glad >> if you could contribute to the pharo-wiki! Don't forget to read the >> contribution guidelines. ;) >> >> We opened a Twitter to announce new entries on the pharo-wiki. >> >> https://twitter.com/PharoOpen >> >> Have a nice day! >> > >

Jan. 30, 2019

Re: [Pharo-users] [ANN] Pharo open documentation

by Offray Vladimir Luna CÃ¡rdenas

Hi Cyril, Thanks for your work on this. Just to clarify, the Pharo Wiki is the entry points for all the other documentation projects? If that's the case, should be expected that the Awesome Pharo and Awesome Pharo ML are linked there? Cheers, Offray On 30/1/19 9:00, Cyril Ferlicot wrote: > Hi everyone! > > With some other members of the community we are proud to announce a > new effort on Pharo documentation. > > We launched an organization pharo-open-documentation which is a > user-maintained documentation related to Pharo environment, language, > and libraries. > > Currently it has three main projects: > - pharo-wiki : Wiki related to the Pharo programming language and environment. > - awesome-pharo : A collection of awesome Pharo libraries, tools, > frameworks and software. We want to make this project a reference in > https://github.com/sindresorhus/awesome > - awesome-pharo-ml : List of projects, books, booklets, papers, and > applications related to machine learning, AI, data science in Pharo. > > Contributions are welcomed! > > If you own a cool project in Pharo others could use in their own > projects, send us a PR to awesome-pharo! > If you have knowledge on Pharo or projects of Pharo, we would be glad > if you could contribute to the pharo-wiki! Don't forget to read the > contribution guidelines. ;) > > We opened a Twitter to announce new entries on the pharo-wiki. > > https://twitter.com/PharoOpen > > Have a nice day! >

Jan. 30, 2019

Re: [Pharo-users] PetitParser question

by Tudor Girba

Great. I am happy you found a solution :) Cheers, Doru > On Jan 30, 2019, at 3:37 PM, Konrad Hinsen <konrad.hinsen(a)fastmail.net> wrote: > > Tudor Girba <tudor(a)tudorgirba.com> writes: > >> Would this not work: > > It works. And as much as I hate to admit it, my version of yesterday was > very similar except ... that it lacked a set of parentheses :-( > >> Please note that I used PetitParser2 for this one because it also >> addresses the failure message issue you raised below. However, the >> logic would work in PP1 as well. > > It does, but I ended up switching to PP2 as well to get the right error > messages. > > Thanks a lot, > Konrad. -- www.feenk.com "We cannot reach the flow of things unless we let go."

Jan. 30, 2019

Re: [Pharo-users] PetitParser question

by Konrad Hinsen

Tudor Girba <tudor(a)tudorgirba.com> writes: > Would this not work: It works. And as much as I hate to admit it, my version of yesterday was very similar except ... that it lacked a set of parentheses :-( > Please note that I used PetitParser2 for this one because it also > addresses the failure message issue you raised below. However, the > logic would work in PP1 as well. It does, but I ended up switching to PP2 as well to get the right error messages. Thanks a lot, Konrad.

Jan. 30, 2019

[ANN] Pharo open documentation

by Cyril Ferlicot

Hi everyone! With some other members of the community we are proud to announce a new effort on Pharo documentation. We launched an organization pharo-open-documentation which is a user-maintained documentation related to Pharo environment, language, and libraries. Currently it has three main projects: - pharo-wiki : Wiki related to the Pharo programming language and environment. - awesome-pharo : A collection of awesome Pharo libraries, tools, frameworks and software. We want to make this project a reference in https://github.com/sindresorhus/awesome - awesome-pharo-ml : List of projects, books, booklets, papers, and applications related to machine learning, AI, data science in Pharo. Contributions are welcomed! If you own a cool project in Pharo others could use in their own projects, send us a PR to awesome-pharo! If you have knowledge on Pharo or projects of Pharo, we would be glad if you could contribute to the pharo-wiki! Don't forget to read the contribution guidelines. ;) We opened a Twitter to announce new entries on the pharo-wiki. https://twitter.com/PharoOpen Have a nice day! -- Cyril Ferlicot https://ferlicot.fr

Jan. 30, 2019

No window on OS X

by Hilaire

Hi, DrGeo 18.06 for Mac OSX[1] was built against P6.1 32bits VM (as far I remember). On Mac OS X High Sierra 10.13.6 (17G65), drgeo starts but there is no window. Is there known issues as this one? Thanks, Hilaire [1] https://launchpad.net/drgeo/trunk/18.06/+download/DrGeo.app-18.06a.zip -- Dr. Geo http://drgeo.eu

Jan. 30, 2019