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

Re: [Pharo-project] Is FS loadable in 1.3?

by Sean P. DeNigris

Tudor Girba-2 wrote: > > Please note that the official up-to-date ConfigurationOfFilesystem can be > found in the squeaksource.com/fs repository. > All 311 tests pass for #latestVersion in 1.3-rc. Sweet. -- View this message in context: http://forum.world.st/Is-FS-loadable-in-1-3-tp3961499p3962226.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 1, 2011

[Pharo-project] FS-Help

by Sean P. DeNigris

Include with 1.4? (currently it's not) -- View this message in context: http://forum.world.st/FS-Help-tp3962221p3962221.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 1, 2011

Re: [Pharo-project] Comment Syntax

by Sean P. DeNigris

Schwab,Wilhelm K wrote: > > ...It would be nice if it were portable to other Smalltalks, but it would > be useful. > ... > XP advocates would tell us that we don't need the code and to just delete > it. > The second point is valid, but only applies to a subset of comments. For example, in my case the thing that needs to be commented is Applescript code that provides context for the method. It is part of the documentation, and must contain double quotes to be valid Applescript. -- View this message in context: http://forum.world.st/Comment-Syntax-tp3961451p3962192.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 1, 2011

Re: [Pharo-project] Paradigm change in Smalltalk software engineering visible?

by HernÃ¡n Morales Durand

Kuhn's more than 20 senses of paradigm change? In computer "science"? ... 2011/10/31 Guido Stepken <gstepken(a)googlemail.com>: > Hello! > > Some weeks ago i asked, weather code in Smalltalk is an object too or not. The answers were not that clear as i expected! :-( > > Now i would like to put up the question, if there is a paradigm change in software engineering slowly coming up in the Smalltalk community towards class factory, code, that generates code, that is jitted immediately to generate further classes to finally be instantiated? > > E.g. the regexp compilercompiler SmaCC. How "dense" has a Smalltalk code system to be that it starts to emerge from itself? > > Means: When starts Pharo refactoring its own code or AST parser itself? > > Maybe a too unclear question, but i hope someone can understand what i mean ... :-) > > tnx in advance, Guido Stepken >

Nov. 1, 2011

Re: [Pharo-project] Is FS loadable in 1.3?

by Sean P. DeNigris

Tudor Girba-2 wrote: > > Please note that the official up-to-date ConfigurationOfFilesystem can be > found in the squeaksource.com/fs repository. > Okay, thanks. The one at sqs/MetacelloRepository is the one that I used and it's out-of-date. Sean -- View this message in context: http://forum.world.st/Is-FS-loadable-in-1-3-tp3961499p3962183.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 1, 2011

Re: [Pharo-project] Comment Syntax

by Schwab,Wilhelm K

First a confession: I would not mind seeing such a feature. It would be nice if it were portable to other Smalltalks, but it would be useful. That said, (I can't *believe* I'm writing this... <g>) XP advocates would tell us that we don't need the code and to just delete it. With readily obtainable version history, there is a way to recover from such an action. The rebuttal is that versions can get lost overt time, out-of-sight/out-of-mind, etc.. More times than I care to count, clear dated comments, and commented code, have saved me LOTS of trouble. I think the record is that in about an hour, I fixed a defect that had been lurking for several years. Had I removed old code that wasn't quite right, I'd have been in a real spot. But seeing the failure that arose and things that didn't quite work in the past, I was able to create a working solution. Comments are good. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Lukas Renggli [renggli(a)gmail.com] Sent: Monday, October 31, 2011 5:22 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Comment Syntax The problem is that both #/* and #/* are valid binary operators, so they don't work well for comments. I don't really remember what I proposed a few years ago, although I remember that exactly the same proposal was made. What would work is to use something like "* and *" (or any other double thing that starts with a double quote). Like this the comments could contain double quotes. As a short term solution you can also put your comments into single quotes. Unused string literals are removed by the compiler. Lukas On 31 October 2011 22:00, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Me too. > > Sean lukas proposed a syntax for that in the mailing-list a year ago. > If you find it please resent it. > > Stef > > On Oct 31, 2011, at 9:12 PM, Sean P. DeNigris wrote: > >> Would it be difficult/valuable to create an alternate comment syntax? I often >> find myself wanting to comment a large block itself containing comments. It >> would be nice to have something like C++'s /* */. I feel like this may have >> been brought up before, but couldn't find it searching the lists. >> >> Sean >> >> -- >> View this message in context: http://forum.world.st/Comment-Syntax-tp3961451p3961451.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > > -- Lukas Renggli www.lukas-renggli.ch

Nov. 1, 2011