July 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo 1.1/1.2 and class names in Chinese

by Alexandre Bergel

> I'd even suggest the system to reject names and selectors not in ASCII. I agree for what has to be put in PharoCore and Pharo. However, a user lambda must be able to create a class called MaClassePrÃ©fÃ©rÃ©e if he/she wishes. Every beginner do this... Cheers, Alexandre > > Cheers, > Juan Vuletich > > Alexandre Bergel wrote: >> I have no idea how to help you. But trying to have classes with chinese (or any other alphabet with accents) names is important. >> Even though I personally write all my code in English, many like to write code in their favorite natural language. This is what I see with students for example. >> >> Cheers, >> Alexandre >> >> >> On 28 Jul 2010, at 21:33, empty wrote: >> >> >>> In 1.1 and 1.2, without setting a language environment for Chinese, I am able >>> to use Chinese by setting fonts. It seems to work except for accepting a >>> class named in Chinese will end in a ClassBuilder error of 'Class names must >>> be capitalized'. Well is it a feature(requires language environment being >>> set correctly) or bug? >>> >>> The code located being: >>> >>> validateClassName: aString >>> "Validate the new class name" >>> >>> aString isSymbol >>> ifFalse: [ ^ false ]. >>> aString first canBeGlobalVarInitial ifFalse:[ >>> self error: 'Class names must be capitalized'. >>> ^false]. >>> environ at: aString ifPresent:[:old| >>> (old isKindOf: Behavior) ifFalse:[ >>> self notify: aString asText allBold, ' already exists!\Proceed will store over it.' withCRs]]. >>> ^ true >>> >>> and following the code the problemic method is #canBeGlobalVarInitial: which >>> is found in two classes: >>> in EncodedCharSet class side: >>> canBeGlobalVarInitial: char >>> >>> | leadingChar | >>> leadingChar := char leadingChar. >>> >>> leadingChar = 0 ifTrue: [^ self isUppercase: char]. >>> ^ self isLetter: char. >>> >>> and in LanguageEnvironment >>> >>> canBeGlobalVarInitial: char >>> >>> ^ Unicode canBeGlobalVarInitial: char. >>> >>> I didn't set a Chinese environment and the exception is occured in in >>> EncodedCharSet class since leadingChar is 0 and a Chinese char seems thought >>> to be lowercased. >>> >>> >>> >>> >>> ----- >>> åç¡ä½ åç¡æ³ åç¡å§ >>> -- >>> View this message in context: http://forum.world.st/Pharo-1-1-1-2-and-class-names-in-Chinese-tp2305496p23… >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> ------------------------------------------------------------------------ >> >> >> No virus found in this incoming message. >> Checked by AVG - www.avg.com Version: 9.0.851 / Virus Database: 271.1.1/3030 - Release Date: 07/26/10 15:34:00 >> >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 28, 2010

Re: [Pharo-project] Pharo 1.1/1.2 and class names in Chinese

by Juan Vuletich

Hi Folks, I think that is a mistake. Having Spanish as my mother tongue, I used to code with Spanish names before knowing Smalltalk. So when started using Smalltalk I kept doing it. Later I realized it is a bad idea. In Smalltalk there is no clear distinction between the "vendor libraries" and our own code. Our application specific classes will many times implement methods akin to existing ones in the system. Writing their names in English makes the whole system more consistent. Following this a little bit, it is better if all the code we write is in English too. OTOH, I believe it is ok to write comments in languages other than English (if the code will not be open sourced). I'd even suggest the system to reject names and selectors not in ASCII. Cheers, Juan Vuletich Alexandre Bergel wrote: > I have no idea how to help you. But trying to have classes with chinese (or any other alphabet with accents) names is important. > Even though I personally write all my code in English, many like to write code in their favorite natural language. This is what I see with students for example. > > Cheers, > Alexandre > > > On 28 Jul 2010, at 21:33, empty wrote: > > >> In 1.1 and 1.2, without setting a language environment for Chinese, I am able >> to use Chinese by setting fonts. It seems to work except for accepting a >> class named in Chinese will end in a ClassBuilder error of 'Class names must >> be capitalized'. Well is it a feature(requires language environment being >> set correctly) or bug? >> >> The code located being: >> >> validateClassName: aString >> "Validate the new class name" >> >> aString isSymbol >> ifFalse: [ ^ false ]. >> aString first canBeGlobalVarInitial ifFalse:[ >> self error: 'Class names must be capitalized'. >> ^false]. >> environ at: aString ifPresent:[:old| >> (old isKindOf: Behavior) ifFalse:[ >> self notify: aString asText allBold, >> ' already exists!\Proceed will store over it.' withCRs]]. >> ^ true >> >> and following the code the problemic method is #canBeGlobalVarInitial: which >> is found in two classes: >> in EncodedCharSet class side: >> canBeGlobalVarInitial: char >> >> | leadingChar | >> leadingChar := char leadingChar. >> >> leadingChar = 0 ifTrue: [^ self isUppercase: char]. >> ^ self isLetter: char. >> >> and in LanguageEnvironment >> >> canBeGlobalVarInitial: char >> >> ^ Unicode canBeGlobalVarInitial: char. >> >> I didn't set a Chinese environment and the exception is occured in in >> EncodedCharSet class since leadingChar is 0 and a Chinese char seems thought >> to be lowercased. >> >> >> >> >> ----- >> åç¡ä½ åç¡æ³ åç¡å§ >> -- >> View this message in context: http://forum.world.st/Pharo-1-1-1-2-and-class-names-in-Chinese-tp2305496p23… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.851 / Virus Database: 271.1.1/3030 - Release Date: 07/26/10 15:34:00 > >

July 28, 2010

Re: [Pharo-project] Pharo 1.1/1.2 and class names in Chinese

by Alexandre Bergel

I have no idea how to help you. But trying to have classes with chinese (or any other alphabet with accents) names is important. Even though I personally write all my code in English, many like to write code in their favorite natural language. This is what I see with students for example. Cheers, Alexandre On 28 Jul 2010, at 21:33, empty wrote: > > In 1.1 and 1.2, without setting a language environment for Chinese, I am able > to use Chinese by setting fonts. It seems to work except for accepting a > class named in Chinese will end in a ClassBuilder error of 'Class names must > be capitalized'. Well is it a feature(requires language environment being > set correctly) or bug? > > The code located being: > > validateClassName: aString > "Validate the new class name" > > aString isSymbol > ifFalse: [ ^ false ]. > aString first canBeGlobalVarInitial ifFalse:[ > self error: 'Class names must be capitalized'. > ^false]. > environ at: aString ifPresent:[:old| > (old isKindOf: Behavior) ifFalse:[ > self notify: aString asText allBold, > ' already exists!\Proceed will store over it.' withCRs]]. > ^ true > > and following the code the problemic method is #canBeGlobalVarInitial: which > is found in two classes: > in EncodedCharSet class side: > canBeGlobalVarInitial: char > > | leadingChar | > leadingChar := char leadingChar. > > leadingChar = 0 ifTrue: [^ self isUppercase: char]. > ^ self isLetter: char. > > and in LanguageEnvironment > > canBeGlobalVarInitial: char > > ^ Unicode canBeGlobalVarInitial: char. > > I didn't set a Chinese environment and the exception is occured in in > EncodedCharSet class since leadingChar is 0 and a Chinese char seems thought > to be lowercased. > > > > > ----- > åç¡ä½ åç¡æ³ åç¡å§ > -- > View this message in context: http://forum.world.st/Pharo-1-1-1-2-and-class-names-in-Chinese-tp2305496p23… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 28, 2010

[Pharo-project] Pharo 1.1/1.2 and class names in Chinese

by empty

In 1.1 and 1.2, without setting a language environment for Chinese, I am able to use Chinese by setting fonts. It seems to work except for accepting a class named in Chinese will end in a ClassBuilder error of 'Class names must be capitalized'. Well is it a feature(requires language environment being set correctly) or bug? The code located being: validateClassName: aString "Validate the new class name" aString isSymbol ifFalse: [ ^ false ]. aString first canBeGlobalVarInitial ifFalse:[ self error: 'Class names must be capitalized'. ^false]. environ at: aString ifPresent:[:old| (old isKindOf: Behavior) ifFalse:[ self notify: aString asText allBold, ' already exists!\Proceed will store over it.' withCRs]]. ^ true and following the code the problemic method is #canBeGlobalVarInitial: which is found in two classes: in EncodedCharSet class side: canBeGlobalVarInitial: char | leadingChar | leadingChar := char leadingChar. leadingChar = 0 ifTrue: [^ self isUppercase: char]. ^ self isLetter: char. and in LanguageEnvironment canBeGlobalVarInitial: char ^ Unicode canBeGlobalVarInitial: char. I didn't set a Chinese environment and the exception is occured in in EncodedCharSet class since leadingChar is 0 and a Chinese char seems thought to be lowercased. ----- åç¡ä½ åç¡æ³ åç¡å§ -- View this message in context: http://forum.world.st/Pharo-1-1-1-2-and-class-names-in-Chinese-tp2305496p23… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 28, 2010

Re: [Pharo-project] help with Glamour

by Alexandre Bergel

Hi Felipe, No idea, but this is good to see you here! Alexandre On 28 Jul 2010, at 18:47, Felipe Ignacio Valverde Campos wrote: > Hi, i'm beginner on this tools, so i need your help please :) > i have some doubts about Glamour, specificaly with GLMTabulator. > > how can i set the window size ? > and how can i close it without pressing the X ? > > thanks > -- > http://www.dcc.uchile.cl/~fvalverd/public_key.asc > Estudiante de IngenierÃa Civil en ComputaciÃ³n. > Facultad de Ciencias FÃsicas y MatemÃ¡ticas. > Universidad de Chile. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 28, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo by Example on Amazon.com

by Marcus Denker

On Jul 28, 2010, at 6:56 PM, laurent laffont wrote: > On Wed, Jul 28, 2010 at 4:16 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Pharo by Example can now finally be ordered at Amazon.com: > > http://www.amazon.com/Pharo-Example-Oscar-Nierstrasz/dp/3952334146/ > > (the availability at Amazon should mean that it is orderable at any bookstore *and* orderable > for libraries world-wide). > > IMHO there should be more informations about the book on Amazon page, pictures, table of contents, bio of authors .... actually it's not very attractive.I buy most of the books on Amazon and I'm often guided by quantity and quality of informations and reviews of the books. So I think it's important. > > Is this generated automatically from Lulu or is it possible to update the page ? sadly it's automatically generated. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 28, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo by Example on Amazon.com

by laurent laffont

On Wed, Jul 28, 2010 at 4:16 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > Hi, > > Pharo by Example can now finally be ordered at Amazon.com: > > http://www.amazon.com/Pharo-Example-Oscar-Nierstrasz/dp/3952334146/ > > (the availability at Amazon should mean that it is orderable at any > bookstore *and* orderable > for libraries world-wide). > IMHO there should be more informations about the book on Amazon page, pictures, table of contents, bio of authors .... actually it's not very attractive.I buy most of the books on Amazon and I'm often guided by quantity and quality of informations and reviews of the books. So I think it's important. Is this generated automatically from Lulu or is it possible to update the page ? Anyway, the availability on Amazon is a good step forward. Cheers, Laurent > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

July 28, 2010

[Pharo-project] help with Glamour

by Felipe Ignacio Valverde Campos

Hi, i'm beginner on this tools, so i need your help please :) i have some doubts about Glamour, specificaly with GLMTabulator. how can i set the window size ? and how can i close it without pressing the X ? thanks -- http://www.dcc.uchile.cl/~fvalverd/public_key.asc Estudiante de IngenierÃa Civil en ComputaciÃ³n. Facultad de Ciencias FÃsicas y MatemÃ¡ticas. Universidad de Chile.

July 28, 2010

[Pharo-project] [ANN] Pharo by Example on Amazon.com

by Marcus Denker

Hi, Pharo by Example can now finally be ordered at Amazon.com: http://www.amazon.com/Pharo-Example-Oscar-Nierstrasz/dp/3952334146/ (the availability at Amazon should mean that it is orderable at any bookstore *and* orderable for libraries world-wide). Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 28, 2010

Re: [Pharo-project] ProcessWrapper BUGs

by Levente Uzonyi

On Wed, 28 Jul 2010, Denis Kudriashov wrote: > Hello > > I found bugs in ProcessWrapper > > try > > externalKiosk := ProcessWrapper new. > externalKiosk startWithCommand: 'notepad'. > > Do "externalKiosk terminate" twice. And image crashed without any logs Terminate is the hard way to kill a process. You don't have to use it, if your process can terminate in another way. There's a workaround for this issue in ProcessWrapperTests >> #tearDown : process isRunning ifTrue: [ process terminate ]. > > Do "externalKiosk finalize" twice.And image crashed without any logs but not > immediately. #finalize is not something that you're intended to send. It's a private method, part of the finalization logic. > > Besides I found that multiple starting and terminating ProcessWrapper and > then saving image can corrupt it. And restarting image crashed by some > failure of finalization process in ProcessWrapper plugin. (I see it in crash > log). > > I test it in Pharo 1.1 with stardart and cog VM > It works fine in Squeak trunk (at least for me). I don't know if it works in Pharo, since WeakRegistry works differently than in Squeak. Btw removing the finalization logic is a bad idea because it's totally ok to not send #terminate at all. Without proper finalization you're leaking resources (memory, semaphores, etc) in this case. Levente

July 28, 2010