- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Status of the VM?

by ClÃ©ment Bera

Hello, This is true but this is a work in progress. Right now this feature is not stable. I will keep you in touch. I think in May I may have something stable enough (I will work with Eliot on April) but it will not be on the default VM. It will be available in the default pharo VM at some point but not now (maybe in a year ?). However, you may or may not be able to use it for your profiling tools. The idea is that you can get branch and send information from the previous executions of the method. However, the method needs to be cogged to have information available and once the cogged method is discarded the information is lost. It is really nice for hot spots but I don't know how it could work for a profiling tool. 2014-03-01 17:06 GMT+01:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Hi! > > Stef told me the coming VM will expose some data about the execution to > the image. This will be great for our profiling tools. > What is the status? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

March 1, 2014

Re: [Pharo-dev] pharo --headless in Windows makes a Window show anyway

by Eliot Miranda

On Sat, Mar 1, 2014 at 8:35 AM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > > > > On Sat, Mar 1, 2014 at 8:31 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > >> On Sat, Mar 1, 2014 at 5:12 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: >> >>> >>> >>> >>> On Sat, Mar 1, 2014 at 7:43 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: >>> >>>> When running (from a Zeroconf install): >>>> >>>> pharo --headless Pharo.image >>>> >>>> it looks like that the window is not opening ( or it is opening and >>>> closing so fast that I do not see it). >>>> >>>> Then I have an image with Seaside, Magritte, and other things. >>>> >>>> When doing the same, I do see the window of one second and then it >>>> closes. >>>> >>>> Is it normal to have that window opening? That's annoying for scripts >>>> as it doesn't look good. >>>> >>>> On OSX I do not have this behavior. >>>> >>>> What causes that on Windows? >>>> >>> >>> It's bits in the exe that decide whether it's a console app or a windows >>> app. So, at least with the Cog VM, not sure about the Pharo VM, if you >>> want to run headless you use the SqueakConsole.exe VM instead of the >>> Squeak.exe VM. They're identical except in those bits. Yes the >>> distinction is stupid; unix doesn't need it, but that's Windows. >>> >>> >>> >>>> Phil >>>> >>> >>> >>> >>> -- >>> best, >>> Eliot >>> >> >> >> >> So, there is a different way to build/link for each type in Squeak. Now, >> with Pharo, there is only one exe in Windows. >> Where's that thing in Squeak so that I can try to build the Pharo Windows >> headless version by kind of cloning it? >> >> In the CMakeLists.txt of the PharoVM for the Windows build, I do see: >> >> add_definitions(-march=pentium4 -mwindows -D_MT -msse2 -mthreads -mwin32 >> -mno-rtd -mms-bitfields -mno-accumulate-outgoing-args -D_USE_32BIT_TIME_T >> -D_WIN32_WINNT=0x0501 -DWINVER=0x0501 -DWIN32 -DWIN32_FILE_SUPPORT >> -DNO_ISNAN -DNO_SERVICE -DNO_STD_FILE_SUPPORT -DLSB_FIRST -DVM_NAME="Pharo" >> -DX86 -DSTACK_ALIGN_BYTES=16 -DALLOCA_LIES_SO_USE_GETSP=0 -DENABLE_FAST_BLT >> -g0 -O2 -march=pentium4 -momit-leaf-frame-pointer >> -maccumulate-outgoing-args -funroll-loops -DNDEBUG -DDEBUGVM=0) >> >> There are -mwindows and -mwin32 which look like candidates for that >> switch. >> >> What do I need to use? >> > > -mconsole in place of -mwindows > and of course if you start a console .exe on the desktop Windows creates a console window for it. sad... -- best, Eliot

March 1, 2014

Re: [Pharo-dev] pharo --headless in Windows makes a Window show anyway

by Eliot Miranda

On Sat, Mar 1, 2014 at 8:31 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > On Sat, Mar 1, 2014 at 5:12 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > >> >> >> >> On Sat, Mar 1, 2014 at 7:43 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: >> >>> When running (from a Zeroconf install): >>> >>> pharo --headless Pharo.image >>> >>> it looks like that the window is not opening ( or it is opening and >>> closing so fast that I do not see it). >>> >>> Then I have an image with Seaside, Magritte, and other things. >>> >>> When doing the same, I do see the window of one second and then it >>> closes. >>> >>> Is it normal to have that window opening? That's annoying for scripts as >>> it doesn't look good. >>> >>> On OSX I do not have this behavior. >>> >>> What causes that on Windows? >>> >> >> It's bits in the exe that decide whether it's a console app or a windows >> app. So, at least with the Cog VM, not sure about the Pharo VM, if you >> want to run headless you use the SqueakConsole.exe VM instead of the >> Squeak.exe VM. They're identical except in those bits. Yes the >> distinction is stupid; unix doesn't need it, but that's Windows. >> >> >> >>> Phil >>> >> >> >> >> -- >> best, >> Eliot >> > > > > So, there is a different way to build/link for each type in Squeak. Now, > with Pharo, there is only one exe in Windows. > Where's that thing in Squeak so that I can try to build the Pharo Windows > headless version by kind of cloning it? > > In the CMakeLists.txt of the PharoVM for the Windows build, I do see: > > add_definitions(-march=pentium4 -mwindows -D_MT -msse2 -mthreads -mwin32 > -mno-rtd -mms-bitfields -mno-accumulate-outgoing-args -D_USE_32BIT_TIME_T > -D_WIN32_WINNT=0x0501 -DWINVER=0x0501 -DWIN32 -DWIN32_FILE_SUPPORT > -DNO_ISNAN -DNO_SERVICE -DNO_STD_FILE_SUPPORT -DLSB_FIRST -DVM_NAME="Pharo" > -DX86 -DSTACK_ALIGN_BYTES=16 -DALLOCA_LIES_SO_USE_GETSP=0 -DENABLE_FAST_BLT > -g0 -O2 -march=pentium4 -momit-leaf-frame-pointer > -maccumulate-outgoing-args -funroll-loops -DNDEBUG -DDEBUGVM=0) > > There are -mwindows and -mwin32 which look like candidates for that switch. > > What do I need to use? > -mconsole in place of -mwindows -- best, Eliot

March 1, 2014

Re: [Pharo-dev] ws vs st extensions

by Eliot Miranda

On Sat, Mar 1, 2014 at 7:21 AM, Esteban A. Maringolo <emaringolo(a)gmail.com>wrote: > Workspace serves a particular purpose. > > I use them, as soon as I depend on them I move it a to a method. > > However, the main use I have for them is startup scripts or other > things I run from the command line. They can't be methods, because > they change. > +1. I use them for various things. One is for lots of different launch commands for the VM simulator, which I edit a little bit as I develop or debug. There are launch scripts for the various VMs, various images etc, with expressions to set breakpoints etc. Committing these to methods would end up with an unmanageable mess of methods used only once. Keeping a workspace full of a handful of these is much more manageable. Mine lives in my work image but saving it to a file is something I do occasionally, for example if I want to build a new work image, or remember some specific configuration. Another is for blog posts containing Smalltalk code. It's much easier to copy and paste colourised source into a workspace and convert this to html and paste once into wordpress than to colourise each method, export it and paste it into wordpress. The .ws extension is really useful because it says "this is not source, its an arbitrary bag of expressions". So there's nothing archaic about this. As Esteban says it serves many different purposes that chunk format doesn't. With imagination it can serve new purposes (like the blog post editor). > > Regards! > > ps: I have to read about the process of submitting a change > Esteban A. Maringolo > > > 2014-03-01 4:15 GMT-03:00 Pharo4Stef <pharo4Stef(a)free.fr>: > > > > On 01 Mar 2014, at 00:17, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: > > > >> 2014-02-28 18:26 GMT-03:00 Chris Cunningham <cunningham.cb(a)gmail.com>: > >>> On Fri, Feb 28, 2014 at 6:07 AM, Esteban A. Maringolo < > emaringolo(a)gmail.com> > >>> wrote: > >>>> > >>>> I have a naive question... > >>>> > >>>> Why if the BasicCodeLoader handler looks for .st files does the > >>>> Workpace offer .ws as the default extension? > >>> > >>> Well, the workspace doesn't just use chuck format - in fact, you > rarely put > >>> in chunk format into a workspace (or do you? I certainly don't). > Also, > >>> workspaces allow for dynamic local variables - which normal chunk > loaders > >>> don't. The two things behave differently. .st is explicitly for > runnable > >>> code - workspaces are for more than just code - more of a scratch pad. > >> > >> I know, but the cmd line handler isn't a chunk reader. It compiles the > >> content of the file and evaluate it all at once. And explicitly > >> expects for files with .st extension (I don't understand such > >> restriction). > >> > >> I don't put chunk in a workspace either (actually I don't know how to > >> properly read a chunk file in Pharo). > >> > >> tl;dr Frankly I don't like the .ws extension at all. It's a matter of > habit. :) > >> > >> Regards! > > > > send a fix. > > For me saving workspace in file looks prehistorical age. > > just having method to manage code snippets is much more efficient > > > > > > > >> > >> > >> > >> Esteban A. Maringolo > >> > > > > > > -- best, Eliot

March 1, 2014

Re: [Pharo-dev] pharo --headless in Windows makes a Window show anyway

by phil＠highoctane.be

On Sat, Mar 1, 2014 at 5:12 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > > > > On Sat, Mar 1, 2014 at 7:43 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > >> When running (from a Zeroconf install): >> >> pharo --headless Pharo.image >> >> it looks like that the window is not opening ( or it is opening and >> closing so fast that I do not see it). >> >> Then I have an image with Seaside, Magritte, and other things. >> >> When doing the same, I do see the window of one second and then it closes. >> >> Is it normal to have that window opening? That's annoying for scripts as >> it doesn't look good. >> >> On OSX I do not have this behavior. >> >> What causes that on Windows? >> > > It's bits in the exe that decide whether it's a console app or a windows > app. So, at least with the Cog VM, not sure about the Pharo VM, if you > want to run headless you use the SqueakConsole.exe VM instead of the > Squeak.exe VM. They're identical except in those bits. Yes the > distinction is stupid; unix doesn't need it, but that's Windows. > > > >> Phil >> > > > > -- > best, > Eliot > So, there is a different way to build/link for each type in Squeak. Now, with Pharo, there is only one exe in Windows. Where's that thing in Squeak so that I can try to build the Pharo Windows headless version by kind of cloning it? In the CMakeLists.txt of the PharoVM for the Windows build, I do see: add_definitions(-march=pentium4 -mwindows -D_MT -msse2 -mthreads -mwin32 -mno-rtd -mms-bitfields -mno-accumulate-outgoing-args -D_USE_32BIT_TIME_T -D_WIN32_WINNT=0x0501 -DWINVER=0x0501 -DWIN32 -DWIN32_FILE_SUPPORT -DNO_ISNAN -DNO_SERVICE -DNO_STD_FILE_SUPPORT -DLSB_FIRST -DVM_NAME="Pharo" -DX86 -DSTACK_ALIGN_BYTES=16 -DALLOCA_LIES_SO_USE_GETSP=0 -DENABLE_FAST_BLT -g0 -O2 -march=pentium4 -momit-leaf-frame-pointer -maccumulate-outgoing-args -funroll-loops -DNDEBUG -DDEBUGVM=0) There are -mwindows and -mwin32 which look like candidates for that switch. What do I need to use? TIA Phil

March 1, 2014

Re: [Pharo-dev] pharo --headless in Windows makes a Window show anyway

by Eliot Miranda

On Sat, Mar 1, 2014 at 7:43 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > When running (from a Zeroconf install): > > pharo --headless Pharo.image > > it looks like that the window is not opening ( or it is opening and > closing so fast that I do not see it). > > Then I have an image with Seaside, Magritte, and other things. > > When doing the same, I do see the window of one second and then it closes. > > Is it normal to have that window opening? That's annoying for scripts as > it doesn't look good. > > On OSX I do not have this behavior. > > What causes that on Windows? > It's bits in the exe that decide whether it's a console app or a windows app. So, at least with the Cog VM, not sure about the Pharo VM, if you want to run headless you use the SqueakConsole.exe VM instead of the Squeak.exe VM. They're identical except in those bits. Yes the distinction is stupid; unix doesn't need it, but that's Windows. > Phil > -- best, Eliot

March 1, 2014

Status of the VM?

by Alexandre Bergel

Hi! Stef told me the coming VM will expose some data about the execution to the image. This will be great for our profiling tools. What is the status? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 1, 2014

Versioneer docs?

by phil＠highoctane.be

I am now porting my code to 3.0 I am using Versioneer to look at my configuration as when I do load it in 3.0, it seems that there are some duplicate packages coming in my package-cache and I want to remove these dupes. (Mostly Seaside related). Versioneer is very helpful in representing the configuration. Now, is there any doc about its usage? TIA Phil

March 1, 2014

pharo --headless in Windows makes a Window show anyway

by phil＠highoctane.be

When running (from a Zeroconf install): pharo --headless Pharo.image it looks like that the window is not opening ( or it is opening and closing so fast that I do not see it). Then I have an image with Seaside, Magritte, and other things. When doing the same, I do see the window of one second and then it closes. Is it normal to have that window opening? That's annoying for scripts as it doesn't look good. On OSX I do not have this behavior. What causes that on Windows? Phil

March 1, 2014

Re: [Pharo-dev] ws vs st extensions

by Esteban A. Maringolo

Workspace serves a particular purpose. I use them, as soon as I depend on them I move it a to a method. However, the main use I have for them is startup scripts or other things I run from the command line. They can't be methods, because they change. Regards! ps: I have to read about the process of submitting a change Esteban A. Maringolo 2014-03-01 4:15 GMT-03:00 Pharo4Stef <pharo4Stef(a)free.fr>: > > On 01 Mar 2014, at 00:17, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> 2014-02-28 18:26 GMT-03:00 Chris Cunningham <cunningham.cb(a)gmail.com>: >>> On Fri, Feb 28, 2014 at 6:07 AM, Esteban A. Maringolo <emaringolo(a)gmail.com> >>> wrote: >>>> >>>> I have a naive question... >>>> >>>> Why if the BasicCodeLoader handler looks for .st files does the >>>> Workpace offer .ws as the default extension? >>> >>> Well, the workspace doesn't just use chuck format - in fact, you rarely put >>> in chunk format into a workspace (or do you? I certainly don't). Also, >>> workspaces allow for dynamic local variables - which normal chunk loaders >>> don't. The two things behave differently. .st is explicitly for runnable >>> code - workspaces are for more than just code - more of a scratch pad. >> >> I know, but the cmd line handler isn't a chunk reader. It compiles the >> content of the file and evaluate it all at once. And explicitly >> expects for files with .st extension (I don't understand such >> restriction). >> >> I don't put chunk in a workspace either (actually I don't know how to >> properly read a chunk file in Pharo). >> >> tl;dr Frankly I don't like the .ws extension at all. It's a matter of habit. :) >> >> Regards! > > send a fix. > For me saving workspace in file looks prehistorical age. > just having method to manage code snippets is much more efficient > > > >> >> >> >> Esteban A. Maringolo >> > >

March 1, 2014