- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Adding a new class category

by David RÃ¶thlisberger

> When I create new class with a new subcategory for an existing > package, the OBbrowser is not refreshed (the subcategory is not listed). > Maybe this is something that could be easily fixed ? This is probably because the class cats are cached now in OB... I will have a look at that. David

Feb. 11, 2009

[Pharo-project] DNU error in OB

by Serge Stinckwich

Hi all, i have a DNU error each time i didn't select any category when i open a new OB browser and i search a class with CTRL-F. Cheers, -- Serge Stinckwich IRD - UR 079 Geodes, MSI Team, Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

Feb. 11, 2009

[Pharo-project] Adding a new class category

by Alexandre Bergel

Hi David and others, When I create new class with a new subcategory for an existing package, the OBbrowser is not refreshed (the subcategory is not listed). Maybe this is something that could be easily fixed ? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 11, 2009

Re: [Pharo-project] Bug with RBParser

by Gwenael Casaccio

On Wednesday 11 February 2009 12:08:44 Lukas Renggli wrote: > to the ANSI standard integers do not support an exponent: > > Â Â integer ::= decimalInteger Â | radixInteger > Â Â decimalInteger ::= digits > Â Â digits ::= digit+ > Â Â radixInteger ::= radixSpecifier Â 'r' radixDigits > Â Â radixSpecifier := digits > Â Â radixDigits ::= (digit | uppercaseAlphabetic)+ Ok thanks for this explanation :) I didn't know but the problem is that some classes use this notation ... Cheers, Gwenael Casaccio

Feb. 11, 2009

Re: [Pharo-project] Bug with RBParser

by Lukas Renggli

According to the ANSI standard integers do not support an exponent: integer ::= decimalInteger | radixInteger decimalInteger ::= digits digits ::= digit+ radixInteger ::= radixSpecifier 'r' radixDigits radixSpecifier := digits radixDigits ::= (digit | uppercaseAlphabetic)+ They even state explicitly that '10e10' is not a valid number token. Furthermore floating point numbers do not accept a different radix (or base) and thus are always written in decimal notation: float ::= mantissa [exponentLetter exponent] mantissa ::= digits '.' digits exponent ::= ['-']decimalInteger exponentLetter ::= 'e' | 'd' | 'q' Cheers, Lukas On Wed, Feb 11, 2009 at 11:34 AM, Gwenael Casaccio <mrgwen(a)gmail.com> wrote: > Hi, > > RBParser parseExpression: '2r100e2' > results : 400 should be : 16 > > Cheers, > Gwenael Casaccio > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 11, 2009

[Pharo-project] Bug with RBParser

by Gwenael Casaccio

Hi, RBParser parseExpression: '2r100e2' results : 400 should be : 16 Cheers, Gwenael Casaccio

Feb. 11, 2009

Re: [Pharo-project] Call for UI gripes

by David RÃ¶thlisberger

>>> Also, note, that you need only one instance of such tree in image . >>> You don't have to build this tree over and over again for each browser >>> window on screen :) >> In a way, yes. >> But then OB would basically do what the system itself should do, namely modeling >> packages. I would rather invest in a genuine package model in the system itself than >> let OB build its own persistent package model. A browser should by definition browse >> an existing model and not primarily create, maintain, and make persistently >> accessible a system's model. This would be like a shadow model to what the system >> otherwise uses, Sounds odd to me, although from a performance point of view it would >> make sense. >> > > Well, OB using own tree of meta-nodes (OBXXXXNode & subclasses) to > model different data structures and they relations. Should we expect > from squeak/pharo to use same model? I think no. > So, even if some day we will have categories as first class objects in > system, you still will need to map them to own objects. yes, but that won't be problematic in terms of performance anymore when we can rely on an efficient package model. The traditional system browser not showing packages (no matter whether based on OB or the old Browser class) does not need to use caching or even provide its own persistent shadow system model. Instead it just provides a view on the system model, as it should be. Because what the browser does is really simple: It traverses a tree from packages (or class cats in case of the system browser) down to methods. There shouldn't be a huge overhead if the system model provides efficient access to the entities and its sub-entities (eg. transitions from packages to class cats, to classes, to extended classes, etc.). David

Feb. 11, 2009

Re: [Pharo-project] Problem with linux VM and Pharo

by Provoost, P (Paul)

It happens on OpenSolaris too.Squeak runs fine but Pharo crashes almost immediately. When you look into the source code of sqUnixMemory.c you find a comment in the beginning stating that the memory management here is tricky. If you have plenty of memory a workaround is using the -memory commandline option. The maximum seems to be 2047 (MB)... Maybe someone with enough knowledge (Ian P. ?) can look into this problem? Damien Cassou wrote: > Every 5 minutes or so, my VM crashes and prints: > > squeak: /tmp/squeak-svn/platforms/unix/vm/sqUnixMemory.c:172: > uxGrowMemoryBy: Assertion `newDelta >= 0' failed. > Aborted > > > I'm using Squeak VM from SVN. Does that happen to anyone else? > _____________________________________________________________ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _____________________________________________________________

Feb. 11, 2009

Re: [Pharo-project] Workspace API

by StÃ©phane Ducasse

Then I'm not in favor to load files in workspace or saving contents to file. Workspace snippets are against classes. If you have a nice and fast snippets then you put it in a class and work a bit and you get an little object. And you can even version it Stef On Feb 10, 2009, at 3:49 PM, Keith Hodges wrote: > http://bugs.squeak.org/view.php?id=5669 > > I requested then implemented a reasonable API for opening Workspaces > on > strings and files. I now find that pharo has implemented incompatible > versions of the same. > > Workspace openContents: 'blah'. > > or > > Workspace new > contents: 'blah'; > label: 'Title'; > open. > > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 11, 2009

Re: [Pharo-project] Workspace API

by StÃ©phane Ducasse

Where? When? Keith in the long run it would be nice that yu do not bash us systematically. Yes we have a different way of working but normally this is often by pure lack of time or information that we do not check what exist. Stef On Feb 10, 2009, at 3:49 PM, Keith Hodges wrote: > http://bugs.squeak.org/view.php?id=5669 > > I requested then implemented a reasonable API for opening Workspaces > on > strings and files. I now find that pharo has implemented incompatible > versions of the same. > > Workspace openContents: 'blah'. > > or > > Workspace new > contents: 'blah'; > label: 'Title'; > open. > > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 11, 2009