Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- 3 participants
- 144636 messages
Manifest class values - instance or class side
by Kasper Osterbye
It is unclear if literal values in Manifest classes should be on the instance
side or on the class side.
demarey wrote in the package comments thread on May 6th:
"Data is stored in raw strings in methods (instance side) of the
Manifest."
However, when I look in the actual manifest classes, it seems like the
manifest values (from the rule checker) are stored in the class side.
In our work on package comments, we want to put the package comments in the
manifest classes, but we are uncertain if it should be on the instance or
class side.
--
View this message in context: http://forum.world.st/Manifest-class-values-instance-or-class-side-tp482644…
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
May 15, 2015
New CogVMs available
by Eliot Miranda
at http://www.mirandabanda.org/files/Cog/VM/VM.r3343.
CogVM source as per VMMaker.oscog-eem.1303/r3343
Cogit:
Fix the regression with #== in the StackToRegisterMappingCogit;
a spilled constant must still be dropped from the stack. (fixes the
width:color: MNU)
Since the method zone does not scavenge PICs, the MNU method in an MNU PIC
entry
cannot be young. If it is, void the cache (load 0 instead of the method).
--
best,
Eliot
May 15, 2015
Re: [Pharo-dev] Pharo Screencast By a Ruby Guy
by Ben Coman
On Tue, May 12, 2015 at 5:56 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote:
>
> > On 12 May 2015, at 11:44, Sven Van Caekenberghe <sven(a)stfx.eu> wrote:
> >
> >
> >> On 11 May 2015, at 23:49, Sean P. DeNigris <sean(a)clipperadams.com>
> wrote:
> >>
> >>
> http://devblog.avdi.org/2015/05/11/in-which-i-make-you-hate-ruby-in-7-minut…
> >
> > Not a perfect demo (he could have run the tests from within the
> browser), but nice to see how (some) outsiders think about Pharo
>
> Which brings us to the conclusion, that we have to improve improve dx for
> TDD :)
>
>
>
There have been several comments to the effect, "Everything there was
pretty cool, but when you searched the documentation âby exampleâ, I
literally shouted, âNo way!â, alone here in my office. Thatâs such a
brilliant idea."
Maybe we should transfer the Finder>Examples behaviour to GTSpotter and
promote it more. (I've not got Pharo with me to check. Maybe I remember
some announcement on this, but its not very visible or discoverable). Its
filter might be #howto, similar to #i and #s.
cheers -ben
May 15, 2015
Re: [Pharo-dev] Transcript needs your love
by Ben Coman
>
>
> Le 14/5/15 15:12, Alain Rastoul a écrit :
>
> Le 14/05/2015 02:08, J. Vuletich (mail lists) a écrit :
>>
>>> A port of the code to Pharo is required, as Alain and Stef have shown.
>>> Besides, Cuis doesn't include support for Traits. I think your idea is
>>> very good, and I hope some Pharoer (Alain?) does it.
>>>
>>
>> Hi Juan,
>>
>> I tried Cuis, you did a very nice work here.
>>
>> About porting, I did this first raw port to allow other peoples who
>> complains about pharo transcript to have a look at Cuis Trancript more
>> easily.
>> And apart from a small window inset problem and an initial display Form I
>> probably did not get well (and/or a clip missing somewhere?), it does the
>> same thing than in Cuis.
>>
>> May be we should wait a little so that people can say their word about it
>> too and eventually/if they want/can/... investigate those two morphic
>> porting issues.
>> In the meanwhile, a simple "fix" in the Transcript could be done too
>> (see last Ben's post) with an extra system settings.
>>
>> About sluggishnesh and Transcript speedup , the changes you made in Cuis,
>> as seen in git commits, are a bit intrusive (DateAndTime, AbstractFont,
>> Strikefont ?), I don't think I know pharo enough to report them.
>>
>> Also I experienced another issue that exits in Cuis too:
>>
>> The Transcript overwrite other morphs/windows when showing its contents
>> during do-it
>>
>> After end of execution, the world redisplays correctly
>> but not in Pharo
>>
>> (see attached screen shots)
>>
>>
>>
>
>
On Fri, May 15, 2015 at 3:18 AM, stepharo <stepharo(a)free.fr> wrote:
> Thanks alain for checking.
> I think that we can offer different implementations and let people pick
> the ones they like.
> My goal is to remove direct refer to Transcript from the image so that we
> can plug an implementation and in particular
> the merge of Doru and Norbert/Mine loggers
>
> Stef
>
I don't quite follow "remove direct refer to Transcript". Isn't
"Transcript" effectively a global variable that can already be plugged with
any implementation?
As I've been contemplating the Transcript situation, I keep coming back to
the idea that Transcript should be a client of a broader logging framework,
but wondering how much complication that would to tracing VM simulation.
Further, since the logging framework needs to be threadsafe, rather than
using protected access to a shared datastructure, would it be good to have
a separate "logging" process to consume log entry submissions from multiple
threads, and pass them on to output threads (including Transcript viewer).
Some possible advantages:
* Eliminate complications from priority inversion (
http://en.wikipedia.org/wiki/Priority_inversion)
* Minimise code that log-entry-producer-thread needs to execute/debug into
-- maybe beneficial for VM simulation?
* Minimises execution time in log-entry-producer-thread.
cheers -ben
May 15, 2015
Re: [Pharo-dev] [squeak-dev] Cog VM problem?
by Eliot Miranda
Hi Raymond,
yes, thanks. We have a regression in the code generator due to recent
changes to #== compilation. We're working on it. I hope to have a fix
soon. Apologies for the inconvenience.
For those of you curious why this only affects the V3 VM, not the Spur VM,
the reason is that in Spur the Cogit passes up to 2 argument sends in
registers but in V3 it passes only up to 1 arg sends in registers. In
(borderWidth = style width and:
["Hah! Try understanding this..."
borderColor == style style or:
["#raised/#inset etc"
#simple == style style and: [borderColor = style color]]])
ifFalse:
[style := borderColor isColor
ifTrue: [BorderStyle width: borderWidth color: borderColor]
ifFalse: [(BorderStyle perform: borderColor) width: borderWidth "argh."].
self setProperty: #borderStyle toValue: style].
#simple erroneously ends up getting spilled to the stack, so that when the
send of width:color: to BorderStyle occurs the code generator emits code to
access what it thinks is BorderWidth, but ends up accessing #simple instead.
As I say we're working on it and should have a fix soon.
On Thu, May 14, 2015 at 8:13 AM, Raymond Asselin <jgr.asselin(a)me.com> wrote:
> Cog.app-15.19.3336.tgz
> gave me a Debugger window
>
>
>
> with these artefacts
> This is a MauiDomainMorph
>
>
>
>
>
--
best,
Eliot
May 15, 2015
Default package comment
by Sergio Fedi
Hi guys,
we are adding comments to packages and we would like a feedback from the
community.
What do you suggest for the default package comment?
May 14, 2015
Re: [Pharo-dev] Transcript needs your love
by Alain Rastoul
Le 14/05/2015 21:18, stepharo a écrit :
>
ah, also I saw that you were discussing about do-it in separate
processes. that should be easy to implment IMHO (as a test menu option
to start), with some side effects sure ...
I already mentioned the effectiveProcess not maintained by the inspector
(see fogbuz entry
https://pharo.fogbugz.com/f/cases/15491/Debugger-hangs-vm-on-step-into)
there will be other but may be not that much.
IMHO not only better for user experience, but also a way to explore new
interesting areas
--
Regards,
Alain
May 14, 2015
Re: [Pharo-dev] Transcript needs your love
by Alain Rastoul
Le 14/05/2015 21:18, stepharo a écrit :
> Thanks alain for checking.
> I think that we can offer different implementations and let people pick
> the ones they like.
> My goal is to remove direct refer to Transcript from the image so that
> we can plug an implementation and in particular
> the merge of Doru and Norbert/Mine loggers
>
> Stef
>
I did a cs that I've added in fogbugz entry, I tried to make as few
modifications as possible, so that it remains like original Cuis
implementation.
May be a CS is not the best, but I do not know slices well, I don't know
for example if they are cumulatives, and automaticallly processed as a
fix when the issue is closed, that would not be good here, it is still a
WIP.
May be a repo on Smalltalkhub for that transcript would be better?
I will also edit (or remove, but I don't know how yet) some comments I
added in fogbugz entry, because the mailing list is a better place for
discussions, IIUC it would be better to put only recaps in the fogbugz
entry.
As of today, the integration with Pharo ui is not good : it overwrites
windows etc (as you may have seen in attached screenshots), some work is
needed to make it better.
modifications I made to the original Cuis sources :
- changed all _ with :=
- renamed Transcript to CuisTranscript
- renamed TranscriptMorph to CuisTranscriptMorph
- renamed Transcriptwindow to CuisTranscriptWindow
all in original st files, in order to keep the original stamp (author)
filed-in those st files in pharo
then in pharo:
- filed-in 2 deprecated methods borrowed from squeak 4.5
(Canvas>>image:at: and Rectangle>>outsetBy: ) todo here: find the
replacement
- Modified 4 methods about extent, position etc, and added 2 for
Cuis/Pharo compatibility : to be checked too
and filed out the cs.
--
Regards,
Alain
May 14, 2015
Re: [Pharo-dev] ctrl+a is seen as ctrl+home windows
by Nicolai Hess
I added an issue:
15541 <https://pharo.fogbugz.com/default.asp?15541> windows vm does not
distinguish between ctrl+a and ctrl+home
with a proposed solution:
add $a-1 to the utf32Code field of the event struct, if the keyevent is a
keystroke and the ctrl flag is set
what do you think?
2014-06-30 9:31 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>:
> There is an end key in many keyboards, but some others do not have it. Can
> you (or better, How would you) have ctrl+end in keyboards that doesn't?
>
> Some VMs hardcoded that Ctrl+a = ctrl+home and Ctrl+d = Ctrl+end because
> that's how old terminals work... Now, why have hardcoded ctrl+a = ctrl +
> home, if you can just add a keybinding to ctrl + a?
>
>
> On Mon, Jun 30, 2014 at 8:55 AM, Nicolai Hess <nicolaihess(a)web.de> wrote:
>
>>
>> 2014-06-29 16:34 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>:
>>
>> Hi
>>>
>>> hasSpecialCTRLKeyValue was extracted by me when I hack keybindings to
>>> make ctrl+home and ctrl+end working. Like you I was very surprised by such
>>> keyboard events crappy state.
>>>
>>>
>>
>> So, having ctrl+end and ctrl+d working at the same time is not possible?
>>
>>
>>
>>
>>
>>
>>
>>>
>>>
>>> 2014-06-25 11:22 GMT+04:00 Nicolai Hess <nicolaihess(a)web.de>:
>>>
>>> 2014-06-25 8:58 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>:
>>>>
>>>> There is a problem in the whole keyboard events: they treat keys as
>>>>> characters and vice versa. And that's not always true:
>>>>> - the backspace key is a key, but currently the image interprets it
>>>>> as a character because we only use keypress events in general.
>>>>> - the shift key is a key, and since current image does not use keyup
>>>>> nor keydown, we cannot know if JUST a shift is pressed normally.
>>>>>
>>>>>
>>>>> On Wed, Jun 25, 2014 at 8:53 AM, Sven Van Caekenberghe <sven(a)stfx.eu>
>>>>> wrote:
>>>>>
>>>>>> I don't know anything about event handling, but I once had a look at
>>>>>> Character constants, and found this:
>>>>>>
>>>>>> Character class>>#home
>>>>>> ^ self value: 1
>>>>>>
>>>>>> How about that ?? This is wrong IMHO, ASCII / Unicode value 1 is SOH
>>>>>> (Start of header), sometimes typed as CTRL-A. And there are other strange
>>>>>> constants like that there.
>>>>>>
>>>>>> On 25 Jun 2014, at 08:42, Tudor Girba <tudor(a)tudorgirba.com> wrote:
>>>>>>
>>>>>> > Hi,
>>>>>> >
>>>>>> > I am on Windows, using Pharo 3.0, and I am trying to get the
>>>>>> keybindings to work in Rubric using Windows convention (so, Ctrl instead of
>>>>>> Cmd as a modifier),
>>>>>> >
>>>>>> > It worked reasonably well, but the problem is that somehow Ctrl+a
>>>>>> is mapped to Ctrl+Home. The problem is not specific to Rubric as I can
>>>>>> detect the same behavior in the regular PluggableTextMorph.
>>>>>> >
>>>>>> > Does anyone have an idea of where the problem comes from?
>>>>>> >
>>>>>> > Doru
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > --
>>>>>> > www.tudorgirba.com
>>>>>> >
>>>>>> > "Every thing has its own flow"
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> ctrl+a has the same strange behavior as ctrl+d
>>>> ctrl+a -> ctrl+home
>>>> ctrl+d -> ctrl+end
>>>>
>>>> look at KeyboardEvent>>#hasSpecialCTRLKeyValue
>>>> I am not exactly sure why it is handled that way.
>>>> Replace the method with
>>>>
>>>> hasSpecialCTRLKeyValue
>>>> ^ self controlKeyPressed and: [ keyValue <= 26 ]
>>>>
>>>> now, ctr+a and ctr+d working as expected.
>>>> But I don't know about the side-effects.
>>>>
>>>>
>>>> nicolai
>>>>
>>>>
>>>
>>
>
May 14, 2015
Re: [Pharo-dev] Transcript needs your love
by stepharo
Thanks Clement.
I think that this is true that we should take care about all the hidden
behavior (like creating repo and others).
Stef
Le 11/5/15 17:02, Clément Bera a écrit :
>
>
> 2015-05-11 13:06 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de
> <mailto:nicolaihess@web.de>>:
>
>
> About the GTools, I am sure you know it but, you can disable them
> and work with the good old Workspace and (Eye-)Inspector.
>
>
> Yeah but I could not open the setting browser because you need to be
> able to create a directory to do so and it didn't work. I could not
> either run a Do-it. And EyeInspector also relies on several framework
> so I don't know if it would have worked.
>
> The problem is that going to the point where you reach your bug can
> take a while in debug VMs / the simulator, so having to open the image
> form a working VM to change it and restarting the debug VM / simulator
> takes a while and reduce your productivity greatly compared to a
> squeak image.
>
>
> BTW, how do Traits depend on the bytecode set?
>
> Through markerOrNil. It looks for methods that have the pattern (at
> bytecode level):
>
> selector
> ^ self traitConflict
>
> I will add a fix for that next week. I am doing the next slice on
> things I found were not working in the new bytecode set such as traits.
>
> 2015-05-10 16:43 GMT+02:00 Clément Bera <bera.clement(a)gmail.com
> <mailto:bera.clement@gmail.com>>:
>
>
>
> 2015-05-10 10:37 GMT+02:00 Esteban Lorenzano
> <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>:
>
>
>> On 10 May 2015, at 10:28, Clément Bera
>> <bera.clement(a)gmail.com <mailto:bera.clement@gmail.com>>
>> wrote:
>>
>>
>>
>> 2015-05-09 23:21 GMT+02:00 Tudor Girba
>> <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>>:
>>
>> I do not think there are many people around here that
>> would think that it is irrelevant if the Pharo VM can
>> be developed in Pharo or not. Of course, it is
>> important.
>>
>> So, the discussion should not go to challenge this
>> direction, but rather in you telling us the use cases
>> that you need supported. Please note that I did not
>> say which exact code and how it should look like. I
>> would be interested in learning about the use cases
>> you have. I am quite certain that there are a number
>> of ways to support them and when we work on GT it
>> would be useful to have your use cases on our table.
>>
>>
>> Well I need many lines to explain each point and there
>> are many... I can talk here about a few points. Then I
>> will deal with Esteban for most of them because it is
>> difficult to explain without an interactive discussion.
>>
>>
>> Let me explain the use cases for the Transcript for
>> example. The issues in Pharo are:
>> - The Transcript does not show the stream as it is printed.
>> - The Transcript does not inherit from Stream and thus
>> cannot print with all the methods implemented in Stream.
>> - The Transcript does not allow the user to decorate the
>> text with bold, italic or colors.
>
> sorry⦠you can do that with squeak's transcript?
>
>
> Of course you can.
>
> Try short cut such as Cmd+ 6 or Cmd + 7. Else in the right
> click menu those are the first 3 entries. And you can copy the
> decorated text from Transcript to a Workspace.
>
>
> I am not sure this was changed on purpose. (from my other posts
> about text and fonts and my bug reports) I got the impression some
> people did changes (for cleanup or other reasons) and
> maybe don't know what they changed or didn't not find the time to
> finish the cleanup:
>
> TextMorph righclick does not work anymore.
> Some text emphasis on FT fonts dont work.
> Some TextMorph halos don't work anymore.
>
> I don't think alls this was done on purpose.
>
> For the Transcript shortcuts for example, if we change
> ThreadSafeTranscript to use
> PluggableTextEditorMorph
> instead of
> PluggableTextMorph
>
> cmd+6/7/8/9/0 for changing emphasis/color
> works again.
>
>
> Great ! Well that's one thing that can be fixed easily then. Thanks
> for looking into it.
>
>
> nicolai
>
>>
>> /Usecase 1: Debug printing methods:/ In the VM you have
>> debug printing methods, for example, to print the call
>> stack. These methods are used from the VM simulator, to
>> output the string in the Transcript, and in gdb, to ouput
>> the string in the commandline. The commandline
>> (FileStream stdout in Pharo) and the Squeak Transcript
>> have the same behavior. In Pharo, the Transcript does not
>> inherit from Stream so you can't use the required stream
>> methods to print the debug printing method on the
>> Transcript. In addition, some printing methods print a
>> lot of things and it is important to show the stream as
>> it is printed.
>> For this use-case, we want to keep the smallest
>> difference between the gdb/commadline behavior and the VM
>> simulator/Transcript behavior. If you implement advanced
>> tooling in GT, you therefore need to implement gdb
>> extensions (and lldb extensions because some of us use
>> lldb instead of gdb) and maintain them. I don't think
>> this is a solution.
>>
>> /Usecase 2: CCode generation debugging:/ The
>> CCodeGenerator or Slang translator translates Slang code
>> into C code. Sometimes there is a bug. To debug, instead
>> of generating the faulty C method into an external C
>> file, we print only the faulty C method in the
>> Transcript. Again, we want to keep the lowest difference
>> between the real usecase (printing on the C file) and the
>> debug usecase (printing on the Transcript). In Squeak the
>> FileStream and the Transcript are both Stream, everything
>> works as expected. In Pharo the Transcript has not the
>> expected behavior. Again the method can be long, you can
>> have to wait several seconds, so you'd like the
>> transcript to show the stream as you print it.
>>
>> /Usecase 3: VM simulation:/ Simulating the VM is quite
>> slow, especially the machine code execution simulation.
>> During the simulation process, the UI is non interactive
>> and shows only every while what the simulator is doing in
>> the Transcript. It is important as sometimes when
>> debugging with a test at each machine code instruction it
>> could take several hours before the UI is interactive
>> again and you want to know what is going on. I don't
>> complain that it takes several hours because the
>> alternatives usually require days of debugging and we can
>> launch the VM simulator overnight. In Pharo this does not
>> work as expected.
>>
>> /Usecase 4: In-image machine-code compilation:/ While
>> working in the JIT compiler, sometimes the machine code
>> generated for a bytecoded method is faulty. A common way
>> of debugging it is to print the machine code instructions
>> of the machine code version of the method in the
>> Transcript. It can take a while to print, so it is
>> important to have the Transcript showing the text as it
>> prints. Then, the easiest way of debugging is to look at
>> the machine code and understand what is wrong. For this
>> purpose, we add text decoration to color jump addresses
>> or the instructions where the instruction pointer was
>> when the VM crashed. Then, in squeak, we can easily copy
>> the decorated text to a workspace and generate a new
>> version of the machine code method and compare. In
>> machine code, it is very difficult to do analysis to have
>> more information than just the decompiled text. We add
>> some information while simulating because we know for
>> example the address of specific trampolines, therefore we
>> can print the name of the trampoline when we see that its
>> address is called. Again, sometimes we also have to debug
>> in gdb. In this case, we disassemble the machine code and
>> compare it to the one from in-image compilation, so both
>> printed strings have to be similar (similar text, same
>> chariot returns).
>>
>>
>>
>> Another example is the complexity of the Pharo tools:
>>
>> While developing the VM, I have sometimes a VM partially
>> working or with some plugins not working. In the Squeak
>> image, I can open a workspace on top of this half-working
>> VM and run do-its to see what is working and what is not.
>> In the Pharo image, I can't do anything. You can't open
>> the workspace without opening more advanced tools. I
>> tried to open the Playground, but the first time there
>> was a bug with Traits (Playground use Traits somehow and
>> they were not working due to the new bytecode set not
>> being finished), when that first bug was fixed I could
>> not open it because it crashed simply the VM (I believe
>> it tried to access an external file such as
>> playground-cache). Currently, the Pharo team is trying to
>> build a set of basic tools that have few dependencies to
>> debug a partially working system (that I think you will
>> use to debug glamour while editing it, because you cannot
>> use the glamour inspector if glamour is not working).
>> That would solve this issue.
>> But in no way this point is something that I can do alone
>> to be able to develop the VM in Pharo. This has to be a
>> community effort. And I am saying that because I can't be
>> blamed not to work on the VM in Pharo if to do so I need
>> to spend many months changing Pharo.
>>
>>
>>
>> An example that I believe is a problem in term of the
>> community is the following:
>>
>> I added with Eliot the support for the new bytecode set.
>> Currently, the Squeak image works with the new bytecode
>> set but not the Pharo image. This is because only the
>> Traits are broken, but this is something I could hardly
>> figure out in the Pharo image because nothing is working
>> as the GT tools use Traits. In Squeak I believe there are
>> very few users of Traits so everything worked, and the
>> test suite can reveal that the Traits are broken easily.
>>
>> Currently, the VM process to me is to first make new
>> features work in Squeak, because it is simpler, and then
>> make it work with Pharo, which is more complex. In the
>> last section I discussed how Traits were a problem while
>> implementing the new bytecode set. So what is the long
>> term solution for this issue ?
>> - Will we have a bootstrap process that creates first a
>> Trait-free Kernel and then build the Pharo Kernel out of it ?
>> - Do we forbid people to use Traits in the Pharo Kernel
>> and does that make sense to have Traits in Pharo in this
>> case ?
>> - If we don't do anything, maybe the Traits are only a
>> slight difference with low impact in most cases and it's
>> fine. But maybe there are many small aspects like Traits,
>> such as the Slots the way they were used in GT recently
>> (I don't blame GT or anything, it was just using features
>> in the system that created issues for me), and maybe we
>> reached a point where the complexity between the Pharo
>> kernel and the Squeak kernel is big enough so that a VM
>> developer will first make Squeak works when introducing
>> new features and then deals with the complexity of Pharo ?
>>
>> So, what do we do ? I don't see any simple solution for
>> this issue. And I believe there are people around that
>> see as the only solution for this issue not to have the
>> Pharo VM development process in Pharo because they will
>> see it as a threat to what they want to do with Pharo.
>>
>>
>>
>> Best Doru !
>>
>> PS: I am still using the GTInspector with additional
>> views on graphs created with Roassal everyday and I still
>> enjoy it.
>>
>> PS2: I am on vacation currently because I was getting
>> crazy looking at machine code all day long, so I may not
>> answer as quick as usually during the next week.
>>
>>
>>
>> Cheers,
>> Doru
>>
>>
>>
>> On Sat, May 9, 2015 at 9:31 PM, Clément Bera
>> <bera.clement(a)gmail.com
>> <mailto:bera.clement@gmail.com>> wrote:
>>
>>
>>
>> 2015-05-09 20:25 GMT+02:00 stepharo
>> <stepharo(a)free.fr <mailto:stepharo@free.fr>>:
>>
>>
>>
>> Le 9/5/15 20:16, Clément Bera a écrit :
>>> This whole conversation here shows very well
>>> the point that I tried to explain to Stef
>>> last week. I'm sorry if the mail is a bit
>>> long but I think this discussion has to be
>>> done.
>>>
>>> My whole Smalltalk development life, I have
>>> used Pharo and was happy with it. Now I am
>>> also working in Cog's JIT compiler and for
>>> this specific project, I am working with
>>> Squeak. I don't work with Squeak because I
>>> don't like Pharo, I told you before, I have
>>> worked with Pharo on all my project before,
>>> enjoyed it and if it was possible I would
>>> use Pharo. I work with Squeak because the VM
>>> development tool and development process
>>> simply does *not* work in Pharo. This is not
>>> only because of VM tools working with the
>>> old Morphic not working anymore in Pharo or
>>> details like that, it is also due to deeper
>>> changes in Pharo.
>>>
>>> Stef believes it is important that Pharo is
>>> able to host development for its own VM.
>>> Therefore, I discussed with him and Esteban
>>> about a first list of points that are
>>> necessary for Pharo to support its VM
>>> development in Pharo, which includes this
>>> Transcript behavior.
>>>
>>> As of today, and I am honest here, I believe
>>> that what is required for Pharo to support
>>> the development process of its VM includes
>>> points which goes in the opposite direction
>>> than a few points in the Pharo roadmap, that
>>> people in the Pharo community will see as a
>>> regression, as "an intrusion from the Squeak
>>> philosophy into Pharo", or as forbidding the
>>> integration of features that breaks the VM
>>> development process. Therefore, I believe
>>> the Pharo community would disapprove to make
>>> such changes and I highly doubt that it is
>>> possible to have the development process of the
>>> Pharo VM in Pharo.
>>>
>>> I was thinking that only a few points would
>>> be a problem such as the increasing memory
>>> footprint of the Pharo image that is going
>>> to get worse with the sources that will be
>>> included in the image in the future, whereas
>>> a VM developer needs a small image (See
>>> previous threads in this mailing list where
>>> Hilaire complains about that for example).
>>
>> clement can I ask a simple question?
>> why did I ask guille to work on minikernels
>> and bootstrap for his phd instead on a topic
>> where we can publish?
>> - choice A: lack of idea
>> - choice B: ....
>>
>>
>> I have already stated that you believe that it is
>> important that Pharo is able to host development
>> for its own VM.
>>
>> I am not against what you did and I am very
>> excited with Guille's work.
>>
>> Pharo is community-driven, so I am not asking the
>> question to you only, but to the community.
>>
>>
>>> However, I didn't think that even simple points
>>> like the Transcript behavior discussed here,
>>> which looks like to me as a regression and is
>>> required for VM development, would be seen as an
>>> improvement by a non negligible part of the
>>> community.
>>>
>>> In this mailing-list, the whole Pharo community
>>> is present and can see this discussion. So the
>>> open questions are:
>>>
>>> *Do you want to have the development of the
>>> Pharo VM in Pharo, or do you want the
>>> development of the Pharo VM to remain in Squeak ?*
>>> *Do you think a system that is not good enough
>>> to handle its own VM development is a good system ?*
>>>
>>> I am not willing to go against the will of the
>>> community because I enjoy community-driven
>>> softwares. If the answer is that Pharo should be
>>> able to support its own VM development then as I
>>> started I will help Esteban and Stef to improve
>>> Pharo so that it can support its own VM
>>> development. Now, if the answer is that the
>>> development of the Pharo VM should remain in
>>> Squeak, I will continue developing the VM in
>>> Squeak.
>>>
>>> You are the Pharo community, you are the ones
>>> that make Pharo alive and kicking, so you tell
>>> me what you think we should do.
>>>
>>> Clement
>>>
>>> 2015-05-09 18:23 GMT+02:00 Eliot Miranda
>>> <eliot.miranda(a)gmail.com
>>> <mailto:eliot.miranda@gmail.com>>:
>>>
>>> Hi Ben,
>>>
>>> On May 9, 2015, at 7:41 AM, Ben Coman
>>> <btc(a)openinworld.com
>>> <mailto:btc@openinworld.com>> wrote:
>>>
>>>>
>>>>
>>>> On Sat, May 9, 2015 at 10:09 PM, Ben Coman
>>>> <btc(a)openinworld.com
>>>> <mailto:btc@openinworld.com>> wrote:
>>>>
>>>> From my limited experience bug hunting,
>>>> calling #changed: from a thread other
>>>> than the UI thread is a source of
>>>> evil. There are too many assumptions
>>>> throughout the system that the UI is
>>>> single threaded. Can anyone advise me
>>>> that is not a proper belief?
>>>>
>>>> Then that implies that a Transcript
>>>> implementation where #nextPut: direct
>>>> calls #changed:
>>>> is not appropriate for use with
>>>> multi-threaded applications. In Pharo,
>>>> #changed: is only called from
>>>> #stepGlobal, which is called from
>>>> doOneCycle:. (This came about as a
>>>> last minute bug fix before Pharo 3
>>>> release and maybe could use some cleanup.
>>>>
>>>> Separating the UI from Transcript into
>>>> its own viewer might be a good idea,
>>>> but actually it would not solve Stef's
>>>> case since his code would still be
>>>> running in the UI thread -- unless the
>>>> viewer ran in another thread, which
>>>> would have its own complexities.
>>>>
>>>> I think the point about efficiency is
>>>> significant. The following example...
>>>> Time millisecondsToRun: [ 1000
>>>> timesRepeat: [ Transcript show: 'x' ] ]
>>>> on Squeak 4.5 --> 12749ms
>>>> on Pharo 50029 --> 2ms
>>>>
>>>>
>>>> As a point of comparison, on VW 8.0 -->
>>>> 43817ms
>>>> and so you might guess, VW 8.0 outputs each
>>>> 'x' immediately.
>>>> cheers -ben
>>>
>>> Way to go, Squeak! Actually this is
>>> disappointing. I'm rather frustrated with
>>> Squeak's slow transcript, and was hoping
>>> that VW would demonstrate it could be
>>> faster. Looking at the Squeak implementation
>>> I only see an obvious 30% or so improvement
>>> via tuning. Looks like good performance will
>>> take more work :-/
>>>
>>>
>>>
>>> Eliot (phone)
>>>
>>>
>>
>>
>>
>>
>>
>> --
>> www.tudorgirba.com <http://www.tudorgirba.com/>
>>
>> "Every thing has its own flow"
>>
>>
>
>
>
>
May 14, 2015