January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3595 in pharo: problem starting up with a script on windows

by pharo＠googlecode.com

Comment #5 on issue 3595 by Torsten....(a)astares.de: problem starting up with a script on windows http://code.google.com/p/pharo/issues/detail?id=3595 One bad smell though ... by using "FileDirectory default" the script is looked up RELATIVE TO THE IMAGE PATH not the current directory I'm in in the console shell. But this is a problem of Coral then and a minus compared to other scripting languages...

Jan. 28, 2011

Re: [Pharo-project] Issue 3595 in pharo: problem starting up with a script on windows

by pharo＠googlecode.com

Updates: Status: WontFix Comment #4 on issue 3595 by Torsten....(a)astares.de: problem starting up with a script on windows http://code.google.com/p/pharo/issues/detail?id=3595 We should close it since it is not a bug

Jan. 28, 2011

[Pharo-project] Fwd: Issue 3599 in pharo: Serial Port

by Serge Stinckwich

---------- Forwarded message ---------- From: SÃ©verin Lemaignan <severin.lemaignan(a)laas.fr> Date: 2011/1/28 Subject: Re: [Pharo-project] Issue 3599 in pharo: Serial Port To: Serge Stinckwich <serge.stinckwich(a)gmail.com> Cc: Pharo-project(a)lists.gforge.inria.fr > The quality of the code is not really good, there is a lot of isString > everywhere in order to test if the port is a number or a string > regarding the OS platform used: I did so to avoid to break anything that could already used the com port with integers. If you're confident it's not used (or if it is easy enough to convert it to 'com1', 'com2' strings...) then feel free to remove support for integer. As far as I remember, the underlying system primitive should be able to deal with 'comX' on Windows. Regards, Severin -- Â Â Â Â SÃ©verin Lemaignan - severin.lemaignan(a)laas.fr Â [00] Â Â PhD student on Cognitive Robotics /|__|\ Â LAAS-CNRS - RIS group / Technische Uni MÃ¼nchen - IAS group Â '' Â Â +33561337844 / +498928917780 Â Â Â Â http://www.laas.fr/~slemaign -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

Jan. 28, 2011

Re: [Pharo-project] Issue 3595 in pharo: problem starting up with a script on windows

by pharo＠googlecode.com

Updates: Cc: stephane.ducasse Comment #3 on issue 3595 by Torsten....(a)astares.de: problem starting up with a script on windows http://code.google.com/p/pharo/issues/detail?id=3595 If you debug both you will notice that ProjectLauncher>>startUpAfterLogin has changed. First there is a check if the given argument (the script name/location) has a protocol like http, file or ftp. If not then the url is "manually" adjusted to file-protocol in Pharo 1.1 isUrl ifFalse:[scriptName := 'file:',scriptName]]. So I get 'file:c:\Foo.st' in Pharo 1.1. here and my Script works. In Pharo 1.2 this is replaced by some URI magic that allows for relative paths: "Allow for ../dir/scriptName arguments" scriptName := (FileDirectory default uri resolveRelativeURI: scriptName) asString]]] In my example that just returns 'c:\Foo.st' (since it is now relative) which results in not loading the stuff if you give an absolute path. Note that there is also a comment: "Allow for ../dir/scriptName arguments" I think this was DONE TO NOW SUPPORT RELATIVE PATHS TOO - maybe for Coral scripting system. If you want to give an absolute path you have to use the file protocol since otherwise it is interpreted as a relative path. That is the effect of the change So C:\pharo\core\1.2\Pharo.exe C:\pharo\core\1.2\PharoCore-1.2.image file:c:\Foo.st works without a problem. Since relative paths are now supported too you can also write: C:\pharo\core\1.2\Pharo.exe C:\pharo\core\1.2\PharoCore-1.2.image ../../../../c:\Foo.st So I think this is not a bug, mainly a "not yet documented new feature".

Jan. 28, 2011

Re: [Pharo-project] Issue 3579 in pharo: "declare temp" adds the variable twice

by pharo＠googlecode.com

Updates: Labels: Type-OB Comment #5 on issue 3579 by marcus.d...(a)gmail.com: "declare temp" adds the variable twice http://code.google.com/p/pharo/issues/detail?id=3579 (No comment was entered for this change.)

Jan. 28, 2011

Re: [Pharo-project] Issue 3575 in pharo: [Failing Tests] Package Monticello leaves Obsolete class after tests

by pharo＠googlecode.com

Updates: Summary: [Failing Tests] Package Monticello leaves Obsolete class after tests Comment #3 on issue 3575 by marcus.d...(a)gmail.com: [Failing Tests] Package Monticello leaves Obsolete class after tests http://code.google.com/p/pharo/issues/detail?id=3575 (No comment was entered for this change.)

Jan. 28, 2011

Re: [Pharo-project] Issue 3575 in pharo: [Failing Tests] Package

by pharo＠googlecode.com

Updates: Summary: [Failing Tests] Package Labels: Milestone-1.2-DevImage Comment #2 on issue 3575 by marcus.d...(a)gmail.com: [Failing Tests] Package http://code.google.com/p/pharo/issues/detail?id=3575 Monticello tests do not clean up (why only in Full???)

Jan. 28, 2011

Re: [Pharo-project] Issue 3595 in pharo: problem starting up with a script on windows

by pharo＠googlecode.com

Comment #2 on issue 3595 by Torsten....(a)astares.de: problem starting up with a script on windows http://code.google.com/p/pharo/issues/detail?id=3595 Can confirm this bug: Pharo 1.1: C:\pharo\install10\Pharo.exe C:\pharo\install11\pharo.image c:\Foo.st works and Pharo 1.2 C:\pharo\install10\Pharo.exe C:\pharo\core\1.2\PharoCore-1.2.image c:\Foo.st comes up with the error: 'No content to install' in CodeLoader>>installSourceFiles.

Jan. 28, 2011

Re: [Pharo-project] Issue 3606 in pharo: [1.1.2] [Failing Test] Undeclared in package shout

by pharo＠googlecode.com

Updates: Labels: Type-Shout Comment #1 on issue 3606 by marcus.d...(a)gmail.com: [1.1.2] [Failing Test] Undeclared in package shout http://code.google.com/p/pharo/issues/detail?id=3606 (No comment was entered for this change.)

Jan. 28, 2011

Re: [Pharo-project] Issue 3581 in pharo: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

by pharo＠googlecode.com

Updates: Labels: Milestone-1.2-DevImage Comment #1 on issue 3581 by marcus.d...(a)gmail.com: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3581 (No comment was entered for this change.)

Jan. 28, 2011