November 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] Returning an Error Code from a Headless Script

by Rob Rothwell

Can the current Pharo and VM return an error code from a headless script in the same way similar to a VBScript: WScript.Quit(999) Or...will this take some VM hacking? Thanks! Rob

Nov. 21, 2009

Re: [Pharo-project] LaTeX users: favorite editor??

by StÃ©phane Ducasse

I use texshop for simple documents (but it does not refresh when we do svn up). Else I used texmate but now I use xemacs and it works well with pdf sync and others. On Nov 21, 2009, at 8:39 PM, Schwab,Wilhelm K wrote: > Stef, > > I looked at the PBE page again and noticed a link to the LaTeX sources for the book, which lead me to wonder what editor you use? I recently found TeX Maker, and generally like it. My one complaint is that (so far at least) I have found no analog to texify, which (part of MikTeX) would do everything required to update a document. While that might be painful for "quick" edits to a book, it's great for shorter documents or to ensure that the toc, references, etc. are up to date. > > Bill > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 21, 2009

Re: [Pharo-project] Managing images: new files vs. new folder

by Schwab,Wilhelm K

Dale, I ask because creating a new directory adds a couple of small wrinkles. First, it generally requires that I update my file transfer/backup configuration, or at least fiddle with it more than would be necessary if several images live in the same directory. It also forces me to mess with (thinking Linux here) menu configuration; if images share a common directory, I can simply edit a common shell script to load the new image, and the main menu is blissfully unaware of it. In the transition period, or to run an older image, I will copy/paste into a terminal, but I am too lazy<g> to do that for my "current" image under ordinary conditions. If anybody thinks they have the ultimate answer (or horror stories about doing the wrong thing), I'd like know about it. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Dale Henrichs Sent: Saturday, November 21, 2009 3:16 PM To: Pharo-project(a)lists.gforge.inria.fr Cc: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Managing images: new files vs. new folder Bill, Monticello shouldn't have a problem sharing the package cache, although concurrent access in the package cache directory could be problematic, but you'd have to be in the middle of downloading a package into the cache in one image while accessing the package from the cache in another image... Dale ----- "Wilhelm K Schwab" <bschwab(a)anest.ufl.edu> wrote: | Hello all, | | How do you handle a new version of Pharo? Obvious choices are to | unzip in the same directory with the previous image, and to create an | image-specific directory. I have succesfully put various images in | one folder in the past, but I worry about MC stepping on itself in the | then common package cache. There are some advantages to that | approach, but if MC gets into trouble, it's a bad idea. | | Bill | | | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 21, 2009

Re: [Pharo-project] Interval>>basicAt: fails

by Adrian Lienhard

Why would you want to call #basicAt:? As the comment in Object>>basicAt: says, this works only for indexable objects, and Interval is not indexable. So this looks like the expected behavior to me. Cheers, Adrian On Nov 21, 2009, at 21:32 , Simon Denier wrote: > Try the following (1) > (1 to: 10) at: 2 > returns 2 > > then (2) > (1 to: 10) basicAt: 2 > raises an exception > > It is surprising. > > Problem is that Interval redefines at: > but in (2), the lookup retrieves Object>>basicAt: which only works for > indexable objects (which an interval is not). > > > So Interval should also redefine basicAt: ? > > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 21, 2009

Re: [Pharo-project] Interval>>basicAt: fails

by Martin McClure

Simon Denier wrote: > Try the following (1) > (1 to: 10) at: 2 > returns 2 > > then (2) > (1 to: 10) basicAt: 2 > raises an exception > > It is surprising. > > Problem is that Interval redefines at: > but in (2), the lookup retrieves Object>>basicAt: which only works for > indexable objects (which an interval is not). > > > So Interval should also redefine basicAt: ? I do not find this surprising. The #basic* methods are intended to be fundamental, never overridden, and to reveal the internal structure of an object. This breaks encapsulation, but you need *some* messages that do that or you can't write debugging tools such as inspectors. So it sounds to me like it's correct as is. Regards, -Martin

Nov. 21, 2009

Re: [Pharo-project] O2PackageBrowser broken in Pharo 10495

by Adrian Lienhard

Hi Simon, David has already fixed some issues a week ago (I know he fixed #1476). But there is no new build available yet. Until these new images are available, I've reverted the links on the download page to the previous versions, which do not have the issue of the O2 package browser. David, could you check whether issue 1475 and 1477 may also be fixed already? thanks for reporting Adrian On Nov 21, 2009, at 20:14 , Simon Denier wrote: > Does someone know why the O2 browser suddenly broke in the latest > 10495. It does not look good, especially since there is plenty of > people here at Smalltalks 09 trying to launch Pharo and follow > PharoByExample get stuck pretty quickly. > > This especially for issues 1475, 1476, 1477 > > Perhaps we can simply go back to a previous version of O2 and publish > a new RC, if David does not have time to correct the bugs. > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 21, 2009

[Pharo-project] [update 1.1] #11057

by StÃ©phane Ducasse

11057 ----- - Issue 1472: CrLfStream fails nextPutAll: since latin1map not initialized - Issue 1478: ScriptLoader loadFFI fails with a dependency error - Issue 1486: New test for Behavior

Nov. 21, 2009

[Pharo-project] Interval>>basicAt: fails

by Simon Denier

Try the following (1) (1 to: 10) at: 2 returns 2 then (2) (1 to: 10) basicAt: 2 raises an exception It is surprising. Problem is that Interval redefines at: but in (2), the lookup retrieves Object>>basicAt: which only works for indexable objects (which an interval is not). So Interval should also redefine basicAt: ? -- Simon

Nov. 21, 2009

Re: [Pharo-project] Managing images: new files vs. new folder

by Dale Henrichs

Bill, Monticello shouldn't have a problem sharing the package cache, although concurrent access in the package cache directory could be problematic, but you'd have to be in the middle of downloading a package into the cache in one image while accessing the package from the cache in another image... Dale ----- "Wilhelm K Schwab" <bschwab(a)anest.ufl.edu> wrote: | Hello all, | | How do you handle a new version of Pharo? Obvious choices are to | unzip in the same directory with the previous image, and to create an | image-specific directory. I have succesfully put various images in | one folder in the past, but I worry about MC stepping on itself in the | then common package cache. There are some advantages to that | approach, but if MC gets into trouble, it's a bad idea. | | Bill | | | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 21, 2009

Re: [Pharo-project] LaTeX users: favorite editor??

by Andrey Larionov

I use Kile for Linux. And LiveTeX distribution On Sat, Nov 21, 2009 at 22:39, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Stef, > > I looked at the PBE page again and noticed a link to the LaTeX sources for the book, which lead me to wonder what editor you use? Â I recently found TeX Maker, and generally like it. My one complaint is that (so far at least) I have found no analog to texify, which (part of MikTeX) would do everything required to update a document. Â While that might be painful for "quick" edits to a book, it's great for shorter documents or to ensure that the toc, references, etc. are up to date. > > Bill > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 21, 2009