- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Seaside] Komanche ?

by Ramiro Diaz Trepat

Robert, can you see your port still listening with this command ? sudo lsof -i -P | grep -i listen On Sun, Oct 11, 2009 at 3:53 PM, Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>wrote: > Ah, if Robert still has an image with the issue and if he does not mind > giving it away for autopsy, maybe someone could look at it :)May be John > Macintosh can help us. > > > > On Sun, Oct 11, 2009 at 3:49 PM, Robert Sirois <watchlala(a)hotmail.com>wrote: > >> I'm running the latest mac vm as well. I believe I attempted the same >> things to no avail. >> >> RS >> >> > Date: Sun, 11 Oct 2009 16:39:37 +0200 >> >> > Subject: Re: [Seaside] Komanche ? >> > From: renggli(a)gmail.com >> > To: seaside(a)lists.squeakfoundation.org >> > >> > I use the same configuration with the 4.1.1beta2U VM. >> > >> > Lukas >> > >> > 2009/10/11 Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>: >> > > Correlation does not mean causality, I know. But in my case this >> happened >> > > right after saving my image, although I had saved it many times before >> > > without issues. >> > > Cheers >> > > >> > > >> > > On Sun, Oct 11, 2009 at 3:01 PM, Ramiro Diaz Trepat < >> ramiro(a)diaztrepat.name> >> > > wrote: >> > >> >> > >> Hi Lukas, >> > >> I am using the latest Pharo, and I have loaded Seaside with >> ScriptLoader >> > >> loadSeaside30. I am using it on a Mac with Leopard. >> > >> I have managed to reuse that port, with random tests and I do not >> believe >> > >> there may be causality here, but I will tell you anyway what I did. >> > >> When this happens, I removed the problematic adaptor from the Seaside >> > >> Control Panel and created a new one (on the same port), then I tried >> closing >> > >> the image and restarting and it did not fix the problem. Although >> when I >> > >> closed another non Seaside image I was running and then restarted the >> > >> problematic image it worked. >> > >> I wonder now if it is not a mac vm issue or socket issue. Robert, >> are you >> > >> also running on a mac? >> > >> In spite I got the image working again, it is quite worring because >> we >> > >> don't know the cause when an image stops answering requests (although >> the >> > >> image itself was not hanged at all and kept working fine), and, most >> weird >> > >> of all, there is no exception or trace of a fault happening. This is >> really >> > >> what is making me wonder if it is not a low level socket issue that >> never >> > >> gets to the image for it to throw an exception or anything at all. >> > >> Cheers >> > >> >> > >> r >> > >> >> > >> ps: I'm cross posting to Pharo because I believe this is not a >> Seaside >> > >> issue. >> > >> >> > >> On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois < >> watchlala(a)hotmail.com> >> > >> wrote: >> > >>> >> > >>> I'm using Pharo 1.0.10419, but I'm not sure how to check the other >> two. I >> > >>> think I'm still running 2.9 in the image I checked. >> > >>> >> > >>> RS >> > >>> >> > >>> > Date: Sun, 11 Oct 2009 12:30:37 +0200 >> > >>> > Subject: Re: [Seaside] Komanche ? >> > >>> > From: renggli(a)gmail.com >> > >>> > To: seaside(a)lists.squeakfoundation.org >> > >>> > >> > >>> > I've never seen this problem before. >> > >>> > >> > >>> > What version of Pharo? Kom? Seaside? >> > >>> > >> > >>> > Lukas >> > >>> > >> > >>> > 2009/10/11 Robert Sirois <watchlala(a)hotmail.com>: >> > >>> > > I've also had this problem for quite a while now and have not >> found >> > >>> > > any way to fix the problem either. >> > >>> > > >> > >>> > > RS >> > >>> > > >> > >>> > > Ramiro Diaz Trepat <ramiro(a)diaztrepat.name> wrote: >> > >>> > > >> > >>> > >>Something really strange happened to me more than once now.In a >> > >>> > >> simple dev >> > >>> > >>image (Pharo + Seaside3 + Kom on a Mac) after saving the image >> at >> > >>> > >> some >> > >>> > >>point, Komanche stops answering anything at all, althought the >> port >> > >>> > >> keeps >> > >>> > >>listening (as listed on a terminal). >> > >>> > >>No errors are displayed anywere but the port becomes unusable >> from >> > >>> > >> that >> > >>> > >>point on. >> > >>> > >>If I wish to continue using the same image I have to add another >> > >>> > >> adaptor in >> > >>> > >>the Seaside Control Panel and start again. >> > >>> > >>The "dead" ports never become usable again, not even stopping >> and >> > >>> > >> removing >> > >>> > >>the adaptor and adding a new one. >> > >>> > >>I am not even sure that this is a Komanche issue, as I said no >> error >> > >>> > >> of >> > >>> > >>anykind is visible. >> > >>> > >>Has anyone come across this before? >> > >>> > >>_______________________________________________ >> > >>> > >>seaside mailing list >> > >>> > >>seaside(a)lists.squeakfoundation.org >> > >>> > >> >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > >>> > > >> > >>> > > _______________________________________________ >> > >>> > > seaside mailing list >> > >>> > > seaside(a)lists.squeakfoundation.org >> > >>> > > >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > >>> > > >> > >>> > > >> > >>> > >> > >>> > >> > >>> > >> > >>> > -- >> > >>> > Lukas Renggli >> > >>> > http://www.lukas-renggli.ch >> > >>> > _______________________________________________ >> > >>> > seaside mailing list >> > >>> > seaside(a)lists.squeakfoundation.org >> > >>> > >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > >>> >> > >>> ________________________________ >> > >>> Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign >> up >> > >>> now. >> > >>> _______________________________________________ >> > >>> seaside mailing list >> > >>> seaside(a)lists.squeakfoundation.org >> > >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > >>> >> > >> >> > > >> > > >> > > _______________________________________________ >> > > seaside mailing list >> > > seaside(a)lists.squeakfoundation.org >> > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > > >> > > >> > >> > >> > >> > -- >> > Lukas Renggli >> > http://www.lukas-renggli.ch >> > _______________________________________________ >> > seaside mailing list >> > seaside(a)lists.squeakfoundation.org >> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> ------------------------------ >> Hotmail: Trusted email with Microsoftâs powerful SPAM protection. Sign up >> now. <http://clk.atdmt.com/GBL/go/177141664/direct/01/> >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> >

Oct. 11, 2009

Re: [Pharo-project] [Seaside] Komanche ?

by Ramiro Diaz Trepat

Ah, if Robert still has an image with the issue and if he does not mind giving it away for autopsy, maybe someone could look at it :)May be John Macintosh can help us. On Sun, Oct 11, 2009 at 3:49 PM, Robert Sirois <watchlala(a)hotmail.com>wrote: > I'm running the latest mac vm as well. I believe I attempted the same > things to no avail. > > RS > > > Date: Sun, 11 Oct 2009 16:39:37 +0200 > > > Subject: Re: [Seaside] Komanche ? > > From: renggli(a)gmail.com > > To: seaside(a)lists.squeakfoundation.org > > > > I use the same configuration with the 4.1.1beta2U VM. > > > > Lukas > > > > 2009/10/11 Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>: > > > Correlation does not mean causality, I know. But in my case this > happened > > > right after saving my image, although I had saved it many times before > > > without issues. > > > Cheers > > > > > > > > > On Sun, Oct 11, 2009 at 3:01 PM, Ramiro Diaz Trepat < > ramiro(a)diaztrepat.name> > > > wrote: > > >> > > >> Hi Lukas, > > >> I am using the latest Pharo, and I have loaded Seaside with > ScriptLoader > > >> loadSeaside30. I am using it on a Mac with Leopard. > > >> I have managed to reuse that port, with random tests and I do not > believe > > >> there may be causality here, but I will tell you anyway what I did. > > >> When this happens, I removed the problematic adaptor from the Seaside > > >> Control Panel and created a new one (on the same port), then I tried > closing > > >> the image and restarting and it did not fix the problem. Although > when I > > >> closed another non Seaside image I was running and then restarted the > > >> problematic image it worked. > > >> I wonder now if it is not a mac vm issue or socket issue. Robert, are > you > > >> also running on a mac? > > >> In spite I got the image working again, it is quite worring because we > > >> don't know the cause when an image stops answering requests (although > the > > >> image itself was not hanged at all and kept working fine), and, most > weird > > >> of all, there is no exception or trace of a fault happening. This is > really > > >> what is making me wonder if it is not a low level socket issue that > never > > >> gets to the image for it to throw an exception or anything at all. > > >> Cheers > > >> > > >> r > > >> > > >> ps: I'm cross posting to Pharo because I believe this is not a Seaside > > >> issue. > > >> > > >> On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois < > watchlala(a)hotmail.com> > > >> wrote: > > >>> > > >>> I'm using Pharo 1.0.10419, but I'm not sure how to check the other > two. I > > >>> think I'm still running 2.9 in the image I checked. > > >>> > > >>> RS > > >>> > > >>> > Date: Sun, 11 Oct 2009 12:30:37 +0200 > > >>> > Subject: Re: [Seaside] Komanche ? > > >>> > From: renggli(a)gmail.com > > >>> > To: seaside(a)lists.squeakfoundation.org > > >>> > > > >>> > I've never seen this problem before. > > >>> > > > >>> > What version of Pharo? Kom? Seaside? > > >>> > > > >>> > Lukas > > >>> > > > >>> > 2009/10/11 Robert Sirois <watchlala(a)hotmail.com>: > > >>> > > I've also had this problem for quite a while now and have not > found > > >>> > > any way to fix the problem either. > > >>> > > > > >>> > > RS > > >>> > > > > >>> > > Ramiro Diaz Trepat <ramiro(a)diaztrepat.name> wrote: > > >>> > > > > >>> > >>Something really strange happened to me more than once now.In a > > >>> > >> simple dev > > >>> > >>image (Pharo + Seaside3 + Kom on a Mac) after saving the image at > > >>> > >> some > > >>> > >>point, Komanche stops answering anything at all, althought the > port > > >>> > >> keeps > > >>> > >>listening (as listed on a terminal). > > >>> > >>No errors are displayed anywere but the port becomes unusable > from > > >>> > >> that > > >>> > >>point on. > > >>> > >>If I wish to continue using the same image I have to add another > > >>> > >> adaptor in > > >>> > >>the Seaside Control Panel and start again. > > >>> > >>The "dead" ports never become usable again, not even stopping and > > >>> > >> removing > > >>> > >>the adaptor and adding a new one. > > >>> > >>I am not even sure that this is a Komanche issue, as I said no > error > > >>> > >> of > > >>> > >>anykind is visible. > > >>> > >>Has anyone come across this before? > > >>> > >>_______________________________________________ > > >>> > >>seaside mailing list > > >>> > >>seaside(a)lists.squeakfoundation.org > > >>> > >> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > >>> > > > > >>> > > _______________________________________________ > > >>> > > seaside mailing list > > >>> > > seaside(a)lists.squeakfoundation.org > > >>> > > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > >>> > > > > >>> > > > > >>> > > > >>> > > > >>> > > > >>> > -- > > >>> > Lukas Renggli > > >>> > http://www.lukas-renggli.ch > > >>> > _______________________________________________ > > >>> > seaside mailing list > > >>> > seaside(a)lists.squeakfoundation.org > > >>> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > >>> > > >>> ________________________________ > > >>> Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign > up > > >>> now. > > >>> _______________________________________________ > > >>> seaside mailing list > > >>> seaside(a)lists.squeakfoundation.org > > >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > >>> > > >> > > > > > > > > > _______________________________________________ > > > seaside mailing list > > > seaside(a)lists.squeakfoundation.org > > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > > > > > > > > > > > -- > > Lukas Renggli > > http://www.lukas-renggli.ch > > _______________________________________________ > > seaside mailing list > > seaside(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > ------------------------------ > Hotmail: Trusted email with Microsoftâs powerful SPAM protection. Sign up > now. <http://clk.atdmt.com/GBL/go/177141664/direct/01/> > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >

Oct. 11, 2009

Re: [Pharo-project] crashing systematically the image with the script to create pharo-dev

by StÃ©phane Ducasse

In fact this is not crashing the image primGetPosition: id "Get this files current position." <primitive: 'primitiveFileGetPosition' module: 'FilePlugin'> self primitiveFailed and I do not have the FilePlugin in the resources VM folder Stef On Oct 11, 2009, at 4:00 PM, StÃ©phane Ducasse wrote: > http://code.google.com/p/pharo/issues/list?cursor=1295 > > I tried with 4.2.1 and 4.2.2 then when I open a workspace and execute > part of the script manually my image does not crash.... > > > > <PharoDebug.log> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 11, 2009

Re: [Pharo-project] [BUG]UndefinedObject(Object)>>doesNotUnderstand: #null

by Adrian Lienhard

ok, I will remove it. Adrian On Oct 11, 2009, at 15:57 , StÃ©phane Ducasse wrote: > +1 > > Stef > > On Oct 11, 2009, at 3:26 PM, Lukas Renggli wrote: > >> PrimitiveNode and #primitiveNode is referenced by the AST package. >> Probably used by the NewCompiler. >> >> I suggest to get rid of it. If the NewCompiler uses it, it should be >> packaged with the NewCompiler. #primtiveNode and PrimtiveNode was >> implemented/referenced by the AST package as well, I killed it too >> because it is not used by the Refactoring Engine. >> >> Lukas >> >> 2009/10/11 Adrian Lienhard <adi(a)netstyle.ch>: >>> CompiledMethod>>primitiveNode refers to PrimitiveNode in Pharo-core. >>> This method has no senders. Can it be removed? >>> >>> Adrian >>> >>> >>> CompiledMethod>>primitiveNode >>> >>> | primNode n | >>> primNode := PrimitiveNode new num: (n := self primitive). >>> (n = 117 or: [n = 120]) ifTrue: [ >>> primNode spec: (self literalAt: 1)]. >>> ^ primNode >>> >>> >>> On Oct 6, 2009, at 17:53 , Lukas Renggli wrote: >>> >>>> I think I fixed the issue in the latest AST package. Even >>>> PrimitiveNode is referenced, it is not really needed anywhere. >>>> >>>> Lukas >>>> >>>> On Tuesday, October 6, 2009, Damien Cassou >>>> <damien.cassou(a)gmail.com> >>>> wrote: >>>>> On Tue, Oct 6, 2009 at 8:39 AM, Marcus Denker <denker(a)acm.org> >>>>> wrote: >>>>>> Damien, can you add this to the AST package used in the DEV >>>>>> image? >>>>> >>>>> Done. Thank you >>>>> >>>>> -- >>>>> Damien Cassou >>>>> http://damiencassou.seasidehosting.st >>>>> >>>>> "Lambdas are relegated to relative obscurity until Java makes them >>>>> popular by not having them." James Iry >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> 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

Oct. 11, 2009

Re: [Pharo-project] [Seaside] Komanche ?

by Ramiro Diaz Trepat

Correlation does not mean causality, I know. But in my case this happened right after saving my image, although I had saved it many times before without issues.Cheers On Sun, Oct 11, 2009 at 3:01 PM, Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>wrote: > Hi Lukas,I am using the latest Pharo, and I have loaded Seaside with > ScriptLoader loadSeaside30. I am using it on a Mac with Leopard. > I have managed to reuse that port, with random tests and I do not believe > there may be causality here, but I will tell you anyway what I did. > When this happens, I removed the problematic adaptor from the Seaside > Control Panel and created a new one (on the same port), then I tried closing > the image and restarting and it did not fix the problem. Although when I > closed another non Seaside image I was running and then restarted the > problematic image it worked. > I wonder now if it is not a mac vm issue or socket issue. Robert, are you > also running on a mac? > In spite I got the image working again, it is quite worring because we > don't know the cause when an image stops answering requests (although the > image itself was not hanged at all and kept working fine), and, most weird > of all, there is no exception or trace of a fault happening. This is really > what is making me wonder if it is not a low level socket issue that never > gets to the image for it to throw an exception or anything at all. > Cheers > > > r > > > ps: I'm cross posting to Pharo because I believe this is not a Seaside > issue. > > > On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois <watchlala(a)hotmail.com>wrote: > >> I'm using Pharo 1.0.10419, but I'm not sure how to check the other two. I >> think I'm still running 2.9 in the image I checked. >> >> RS >> >> > Date: Sun, 11 Oct 2009 12:30:37 +0200 >> > Subject: Re: [Seaside] Komanche ? >> > From: renggli(a)gmail.com >> > To: seaside(a)lists.squeakfoundation.org >> >> > >> > I've never seen this problem before. >> > >> > What version of Pharo? Kom? Seaside? >> > >> > Lukas >> > >> > 2009/10/11 Robert Sirois <watchlala(a)hotmail.com>: >> > > I've also had this problem for quite a while now and have not found >> any way to fix the problem either. >> > > >> > > RS >> > > >> > > Ramiro Diaz Trepat <ramiro(a)diaztrepat.name> wrote: >> > > >> > >>Something really strange happened to me more than once now.In a simple >> dev >> > >>image (Pharo + Seaside3 + Kom on a Mac) after saving the image at some >> > >>point, Komanche stops answering anything at all, althought the port >> keeps >> > >>listening (as listed on a terminal). >> > >>No errors are displayed anywere but the port becomes unusable from >> that >> > >>point on. >> > >>If I wish to continue using the same image I have to add another >> adaptor in >> > >>the Seaside Control Panel and start again. >> > >>The "dead" ports never become usable again, not even stopping and >> removing >> > >>the adaptor and adding a new one. >> > >>I am not even sure that this is a Komanche issue, as I said no error >> of >> > >>anykind is visible. >> > >>Has anyone come across this before? >> > >>_______________________________________________ >> > >>seaside mailing list >> > >>seaside(a)lists.squeakfoundation.org >> > >>http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > > >> > > _______________________________________________ >> > > seaside mailing list >> > > seaside(a)lists.squeakfoundation.org >> > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > > >> > > >> > >> > >> > >> > -- >> > Lukas Renggli >> > http://www.lukas-renggli.ch >> > _______________________________________________ >> > seaside mailing list >> > seaside(a)lists.squeakfoundation.org >> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> ------------------------------ >> Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign up >> now. <http://clk.atdmt.com/GBL/go/171222985/direct/01/> >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> >

Oct. 11, 2009

Re: [Pharo-project] [Seaside] Komanche ?

by Ramiro Diaz Trepat

Hi Lukas,I am using the latest Pharo, and I have loaded Seaside with ScriptLoader loadSeaside30. I am using it on a Mac with Leopard. I have managed to reuse that port, with random tests and I do not believe there may be causality here, but I will tell you anyway what I did. When this happens, I removed the problematic adaptor from the Seaside Control Panel and created a new one (on the same port), then I tried closing the image and restarting and it did not fix the problem. Although when I closed another non Seaside image I was running and then restarted the problematic image it worked. I wonder now if it is not a mac vm issue or socket issue. Robert, are you also running on a mac? In spite I got the image working again, it is quite worring because we don't know the cause when an image stops answering requests (although the image itself was not hanged at all and kept working fine), and, most weird of all, there is no exception or trace of a fault happening. This is really what is making me wonder if it is not a low level socket issue that never gets to the image for it to throw an exception or anything at all. Cheers r ps: I'm cross posting to Pharo because I believe this is not a Seaside issue. On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois <watchlala(a)hotmail.com>wrote: > I'm using Pharo 1.0.10419, but I'm not sure how to check the other two. I > think I'm still running 2.9 in the image I checked. > > RS > > > Date: Sun, 11 Oct 2009 12:30:37 +0200 > > Subject: Re: [Seaside] Komanche ? > > From: renggli(a)gmail.com > > To: seaside(a)lists.squeakfoundation.org > > > > > I've never seen this problem before. > > > > What version of Pharo? Kom? Seaside? > > > > Lukas > > > > 2009/10/11 Robert Sirois <watchlala(a)hotmail.com>: > > > I've also had this problem for quite a while now and have not found any > way to fix the problem either. > > > > > > RS > > > > > > Ramiro Diaz Trepat <ramiro(a)diaztrepat.name> wrote: > > > > > >>Something really strange happened to me more than once now.In a simple > dev > > >>image (Pharo + Seaside3 + Kom on a Mac) after saving the image at some > > >>point, Komanche stops answering anything at all, althought the port > keeps > > >>listening (as listed on a terminal). > > >>No errors are displayed anywere but the port becomes unusable from that > > >>point on. > > >>If I wish to continue using the same image I have to add another > adaptor in > > >>the Seaside Control Panel and start again. > > >>The "dead" ports never become usable again, not even stopping and > removing > > >>the adaptor and adding a new one. > > >>I am not even sure that this is a Komanche issue, as I said no error of > > >>anykind is visible. > > >>Has anyone come across this before? > > >>_______________________________________________ > > >>seaside mailing list > > >>seaside(a)lists.squeakfoundation.org > > >>http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > > > _______________________________________________ > > > seaside mailing list > > > seaside(a)lists.squeakfoundation.org > > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > > > > > > > > > > > -- > > Lukas Renggli > > http://www.lukas-renggli.ch > > _______________________________________________ > > seaside mailing list > > seaside(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > ------------------------------ > Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign up > now. <http://clk.atdmt.com/GBL/go/171222985/direct/01/> > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >

Oct. 11, 2009

[Pharo-project] crashing systematically the image with the script to create pharo-dev

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/list?cursor=1295 I tried with 4.2.1 and 4.2.2 then when I open a workspace and execute part of the script manually my image does not crash....

Oct. 11, 2009

Re: [Pharo-project] [BUG]UndefinedObject(Object)>>doesNotUnderstand: #null

by StÃ©phane Ducasse

+1 Stef On Oct 11, 2009, at 3:26 PM, Lukas Renggli wrote: > PrimitiveNode and #primitiveNode is referenced by the AST package. > Probably used by the NewCompiler. > > I suggest to get rid of it. If the NewCompiler uses it, it should be > packaged with the NewCompiler. #primtiveNode and PrimtiveNode was > implemented/referenced by the AST package as well, I killed it too > because it is not used by the Refactoring Engine. > > Lukas > > 2009/10/11 Adrian Lienhard <adi(a)netstyle.ch>: >> CompiledMethod>>primitiveNode refers to PrimitiveNode in Pharo-core. >> This method has no senders. Can it be removed? >> >> Adrian >> >> >> CompiledMethod>>primitiveNode >> >> | primNode n | >> primNode := PrimitiveNode new num: (n := self primitive). >> (n = 117 or: [n = 120]) ifTrue: [ >> primNode spec: (self literalAt: 1)]. >> ^ primNode >> >> >> On Oct 6, 2009, at 17:53 , Lukas Renggli wrote: >> >>> I think I fixed the issue in the latest AST package. Even >>> PrimitiveNode is referenced, it is not really needed anywhere. >>> >>> Lukas >>> >>> On Tuesday, October 6, 2009, Damien Cassou <damien.cassou(a)gmail.com> >>> wrote: >>>> On Tue, Oct 6, 2009 at 8:39 AM, Marcus Denker <denker(a)acm.org> >>>> wrote: >>>>> Damien, can you add this to the AST package used in the DEV image? >>>> >>>> Done. Thank you >>>> >>>> -- >>>> Damien Cassou >>>> http://damiencassou.seasidehosting.st >>>> >>>> "Lambdas are relegated to relative obscurity until Java makes them >>>> popular by not having them." James Iry >>>> >>>> _______________________________________________ >>>> 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 >>> >>> _______________________________________________ >>> 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 >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 11, 2009

[Pharo-project] Error getting parseTree formattedCode

by StÃ©phane Ducasse

> From: Lukas Renggli <renggli(a)gmail.com> > Date: October 11, 2009 3:27:38 PM GMT+02:00 > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Error getting parseTree formattedCode > Reply-To: Pharo-project(a)lists.gforge.inria.fr > > > The AST package is in an desolate state. There are dozens of methods > that are never used or broken. Part of the NewCompiler infrastructure > is merged into the AST package, so it is not exactly easy to see what > parts are used, what parts are covered by tests, and what parts are > obsolete. > > Lukas argh. Thanks lukas for the update. Stef

Oct. 11, 2009

[Pharo-project] Fwd: [ANN] new pharo core uploaded based on 10470

by StÃ©phane Ducasse

Oct. 11, 2009