- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Some new bindings for native emulation stuff

by ducasse

> That is pretty awesome. Couldnât be an constraint umbrella for VMMaker. Guille is doing that to see if we can reduce the number of plugin and how to build tools to support assembly generation :) And also to be able to write much nicer tests (I mean with real assertions and not transcript show: ;) > This way it would be possible to write tests that check for resulting code. Or writing tests for the JIT (does sista has something like this). Could be one step closer to a deterministic code generation, no? :) Stef > > Norbert > > Am 02.08.2019 um 18:09 schrieb Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>>: > >> Hi everybody, >> >> Iâve been playing around with machine code simulation this last week and Iâve made bindings for the unicorn library and the llvm disassembler: >> >> https://github.com/guillep/pharo-unicorn <https://github.com/guillep/pharo-unicorn> >> https://github.com/guillep/pharo-llvmDisassembler <https://github.com/guillep/pharo-llvmDisassembler> >> >> Funny thing: both support lots of platforms (x86 and arm both 32 and 64 bits and moreâ¦). So out of the box we can simulate and disassemble lots of platforms. >> >> And in one afternoon Iâve played with them to do a native debugger with Spec2 just for fun. >> Hope this evolves a bit more soon, and that it helps somebody. >> >> Guille >> >> <PastedGraphic-5.png> >>

Aug. 3, 2019

[Pharo 8.0] Build #592: Add option to rename parameters when extract a method

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #592 was: FAILURE. The Pull Request #4168 was integrated: "Add option to rename parameters when extract a method" Pull request url: https://github.com/pharo-project/pharo/pull/4168 Issue Url: https://github.com/pharo-project/pharo/issues/RenameParametersVersion2 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 3, 2019

Re: [Pharo-dev] Some new bindings for native emulation stuff

by Norbert Hartl

That is pretty awesome. Couldnât be an constraint umbrella for VMMaker. This way it would be possible to write tests that check for resulting code. Or writing tests for the JIT (does sista has something like this). Could be one step closer to a deterministic code generation, no? Norbert > Am 02.08.2019 um 18:09 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi everybody, > > Iâve been playing around with machine code simulation this last week and Iâve made bindings for the unicorn library and the llvm disassembler: > > https://github.com/guillep/pharo-unicorn > https://github.com/guillep/pharo-llvmDisassembler > > Funny thing: both support lots of platforms (x86 and arm both 32 and 64 bits and moreâ¦). So out of the box we can simulate and disassemble lots of platforms. > > And in one afternoon Iâve played with them to do a native debugger with Spec2 just for fun. > Hope this evolves a bit more soon, and that it helps somebody. > > Guille > > <PastedGraphic-5.png> >

Aug. 3, 2019

[Pharo 8.0] Build #591: Add submenu, and new shortcuts

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #591 was: SUCCESS. The Pull Request #4167 was integrated: "Add submenu, and new shortcuts" Pull request url: https://github.com/pharo-project/pharo/pull/4167 Issue Url: https://github.com/pharo-project/pharo/issues/AddSubmenu Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 3, 2019

Re: [Pharo-dev] [ANN] Pharo Harbour

by Torsten Bergmann

Hi ClÃ©ment, yes - having a better FileBrowser and a FileDialog closer together makes sense. You can freely use the code / project or reuse it for other implementation. Thats why I opened the repo to public. Unfortunately no time to work on it or help the next weeks. Bye Torsten > Gesendet: Donnerstag, 01. August 2019 um 10:17 Uhr > Von: "CafeKrem" <dutriezcle(a)gmail.com> > An: pharo-dev(a)lists.pharo.org > Betreff: Re: [Pharo-dev] [ANN] Pharo Harbour > > Hello Torsten, > > It's ClÃ©ment, actually, I'm working on the FileDialog ( of Peter ) so I will > merge your FileBrowser with my FileDialog. > > Thanks. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

Aug. 2, 2019

Some new bindings for native emulation stuff

by Guillermo Polito

Hi everybody, Iâve been playing around with machine code simulation this last week and Iâve made bindings for the unicorn library and the llvm disassembler: https://github.com/guillep/pharo-unicorn <https://github.com/guillep/pharo-unicorn> https://github.com/guillep/pharo-llvmDisassembler <https://github.com/guillep/pharo-llvmDisassembler> Funny thing: both support lots of platforms (x86 and arm both 32 and 64 bits and moreâ¦). So out of the box we can simulate and disassemble lots of platforms. And in one afternoon Iâve played with them to do a native debugger with Spec2 just for fun. Hope this evolves a bit more soon, and that it helps somebody. Guille

Aug. 2, 2019

Re: [Pharo-dev] Pharo Launcher 1.9.2 Crash

by Sean P. DeNigris

demarey wrote > Could you test it? Yes, works now! Thanks :) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 2, 2019

Re: [Pharo-dev] P8 voyage not installing, error probably in magritte

by Martin Dias

On Thu, Aug 1, 2019 at 6:04 PM Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sanjay Minni wrote > > failure is probably in magritte > > Can you give more specifics? Where is voyage installing Magritte from? > Active development has recently moved to GH Hi Sean, it loads with this uri: github://magritte-metamodel/magritte:v3.5.3/source source: https://github.com/pharo-nosql/voyage/blob/master/mc/BaselineOfVoyage.packa… MartÃn > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Aug. 2, 2019

Re: [Pharo-dev] Pharo Launcher 1.9.2 Crash

by Christophe Demarey

Hi Sean, I suspect a build problem on the CI server. I did a new build with the same files and it works ok for me on Mac OS 10.11.4 and 10.14.6. Could you test it? Itâs updated on files.pharo.org. Thanks for the report, Christophe. > Le 26 juil. 2019 Ã 15:14, Sean P. DeNigris <sean(a)clipperadams.com> a Ã©crit : > > PharoLauncher-1.9.2-x64.dmg does not open on Mac OS 10.14.1. Crash dump shows > Freetype related: > > Segmentation fault Fri Jul 26 09:07:17 2019 > > VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git > Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 > Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git > > C stack backtrace & registers: > rax 0x0000000111ae3be0 rbx 0x00000001121a1878 rcx 0x0000000000000000 rdx > 0x000000000000018c > rdi 0x0000000111ae3be0 rsi 0x0000000111ae3be0 rbp 0x00007ffee922c1b0 rsp > 0x00007ffee922c1b0 > r8 0x0000000000000000 r9 0x0000000000000000 r10 0x0000000106a935a0 r11 > 0x0000000111ae3be0 > r12 0x0000000000000000 r13 0x0000000000000010 r14 0x0000000000000000 r15 > 0x0000000000000000 > rip 0x00007fff67353dd0 > 0 libsystem_platform.dylib 0x00007fff67353dd0 > _platform_memmove$VARIANT$Haswell + 240 > 1 Pharo 0x0000000106a25642 reportStackState > + 952 > 2 Pharo 0x0000000106a25987 sigsegv + 174 > 3 libsystem_platform.dylib 0x00007fff67356b3d _sigtramp + 29 > 4 ??? 0x0000000000000000 0x0 + 0 > 5 Pharo 0x0000000106a5e5aa > primitiveCalloutWithArgs + 164 > > Smalltalk stack dump: > 0x7ffee923a2d0 M LibC>memCopy:to:size: 0x10ec722d8: a(n) LibC > 0x7ffee923a318 M LibC class>memCopy:to:size: 0x10e4c65e0: a(n) LibC > class > 0x7ffee923a380 I ExternalAddress>copyFrom:to: 0x111bab200: a(n) > ExternalAddress > 0x111baea18 s FreeTypeFace(FT2Face)>renderGlyphIntoForm:pixelMode: > 0x111bbc5b8 s FreeTypeFace(FT2Face)>renderGlyphIntoForm: > 0x111bc2db0 s > FreeTypeSubPixelAntiAliasedGlyphRenderer>renderStretchedGlyph:depth:subpixelPosition:font: > 0x111bc6a70 s > FreeTypeSubPixelAntiAliasedGlyphRenderer>subGlyphOf:colorValue:mono:subpixelPosition:font: > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Aug. 2, 2019

Re: [Pharo-dev] [FileReference] why this class don't provide a method isAHiddenFile ?

by ducasse

It would be good to encapsulate this behavior may be with double dispatch with the platform. Else clients end up to be forced to check. Stef > On 1 Aug 2019, at 21:22, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > On Thu, 1 Aug 2019 at 20:51, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >> >> I imagine because it is quite a rare edge-case use and is not easy to implement: >> - for Linux you check for dot >> - for Windows you need to either modify the VM (see File class>>lookupDirectory:filename: to provide more information), or directly use WinAPI from Pharo to retrieve the hidden file attribute >> - for MacOS it is my understanding that you need to do both of the above and then some >> >> Peter >> > > As Peter wrote, this hasn't been requested much, but... > > In Pharo 8: > > (aFileReference entry statAttributes at: 13) anyMask: 16r2 > > Will answer a boolean indicating whether it is hidden or not (only on Windows). > > "aFileReference entry statAttributes at: 13" is the > WIN32_FILE_ATTRIBUTE_DATA: > https://docs.microsoft.com/en-us/windows/win32/fileio/file-attribute-consta… > > HTH, > Alistair >

Aug. 2, 2019