July 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Voyage] #selectOne: and #selectMany: with a block as the argument

by StÃ©phane Ducasse

On Jul 6, 2013, at 11:16 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > sure :) > > I will add a blog post on "voyage advanced queries" too :) too if you want but we could also focus on the chapter because we can be multiple people to edit it while your blog you are alone. Stef > > Esteban > > On Jul 6, 2013, at 10:52 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> esteban could you take some time to add this information to the Voyage chapter? >> >> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ >> >> add the information in any format and I can make it run. >> >> https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english >> >> Stef >> >> >> >> On Jul 4, 2013, at 7:49 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> you have different constructions: >>> >>> { $gt: { "number_field": 42 } } >>> >>> and so on... always with dictionaries (bah, json structs). >>> >>> as a query language it kinda sucks... but well... is how it is :) >>> >>> On Jul 4, 2013, at 7:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>>> Ok but how do I map conceptual a query to a dictionary >>>> >>>> Do I guess right that there is an exact match >>>> >>>> selectOne: { id -> 10} asDictionary >>>> >>>> will match id = 10 >>>> >>>> Now we can only do exact mathc? >>>> >>>> name matches: 'stef*' >>>> >>>> >>>> On Jul 4, 2013, at 6:04 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>>> >>>>> Stef, >>>>> >>>>> You're asking the other Esteban, but having used Voyage and Mongo I >>>>> think I can answer this. >>>>> >>>>> Mongo receives a JSON object to do all the query filtering. For a >>>>> simple lookup it is has a simple structre, as the query gets more >>>>> complex it gets esoteric as well (with "special" MongoDB keys in the >>>>> format of "$key"). >>>>> >>>>> Because the simplest map we have to a JSON Object is the Dictionary, I >>>>> guess that's why it ends up being converted to a Dictionary, which in >>>>> turn gets converted to JSON and/or BSON. >>>>> >>>>> Regards, >>>>> >>>>> Esteban A. Maringolo >>>>> >>>>> >>>>> 2013/7/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>>>> >>>>>> On Jul 4, 2013, at 2:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>>> >>>>>> Hi :) >>>>>> >>>>>> can you check if you have the "MongoQueries" package installed? >>>>>> >>>>>> cheers, >>>>>> Esteban >>>>>> >>>>>> ps: please notice that in anycase you will not be able to execute >>>>>> >>>>>> [ :each | each name first = $X ] >>>>>> >>>>>> because the MongoQueries package just translates the block into a >>>>>> mongo-query which is a dictionary (a JSON expression). But you will found >>>>>> some ways to help you, some special keywords like #in: and #where: (you can >>>>>> see how they work in the tests) >>>>>> >>>>>> >>>>>> esteban >>>>>> how a dictionary is used to work as a block for a query? >>>>>> Can you explain because I would have thought that the first line did not >>>>>> work and the second would work. >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Jul 4, 2013, at 2:17 PM, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>> Hi! >>>>>> >>>>>> I realize probably only Esteban will be able to answer, but I prefer to >>>>>> write to the list so the mail is logged and other people can benefit from >>>>>> it. >>>>>> >>>>>> I'm trying to use blocks as arguments for #selectOne: and #selectMany:, but >>>>>> it doesn't seem to work. Here's my code: >>>>>> >>>>>> MyClass selectOne: { #name -> 'Some name' } asDictionary. >>>>>> MyClass selectOne: [ :each | each name = 'Some name' ]. >>>>>> >>>>>> >>>>>> The first one works, but the second one raises a VOMongoConnectionError. >>>>>> >>>>>> Also: >>>>>> >>>>>> MyClass selectMany: { #name -> 'Some name' } asDictionary. >>>>>> MyClass selectMany: [ :each | each name = 'Some name' ]. >>>>>> >>>>>> >>>>>> The first does work, the second one doesn't, which prevents me from writing >>>>>> more useful stuff like: >>>>>> >>>>>> MyClass selectMany: [ :each | each name first = $P ]. >>>>>> >>>>>> Any idea why this could be failing? I've the latest stable version loaded >>>>>> via: >>>>>> >>>>>> Gofer it >>>>>> url: 'http://smalltalkhub.com/mc/estebanlm/Voyage/main'; >>>>>> package: 'ConfigurationOfVoyageMongo'; >>>>>> load. >>>>>> (Smalltalk at: #ConfigurationOfVoyageMongo) load. >>>>>> >>>>>> Thanks! :) >>>>>> >>>>>> Bernat. >>>>>> >>>>>> -- >>>>>> Bernat Romagosa. >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >>> >> >> > >

July 6, 2013

Re: [Pharo-users] [Voyage] #selectOne: and #selectMany: with a block as the argument

by Esteban Lorenzano

sure :) I will add a blog post on "voyage advanced queries" too :) Esteban On Jul 6, 2013, at 10:52 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > esteban could you take some time to add this information to the Voyage chapter? > > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ > > add the information in any format and I can make it run. > > https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english > > Stef > > > > On Jul 4, 2013, at 7:49 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> you have different constructions: >> >> { $gt: { "number_field": 42 } } >> >> and so on... always with dictionaries (bah, json structs). >> >> as a query language it kinda sucks... but well... is how it is :) >> >> On Jul 4, 2013, at 7:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Ok but how do I map conceptual a query to a dictionary >>> >>> Do I guess right that there is an exact match >>> >>> selectOne: { id -> 10} asDictionary >>> >>> will match id = 10 >>> >>> Now we can only do exact mathc? >>> >>> name matches: 'stef*' >>> >>> >>> On Jul 4, 2013, at 6:04 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>> >>>> Stef, >>>> >>>> You're asking the other Esteban, but having used Voyage and Mongo I >>>> think I can answer this. >>>> >>>> Mongo receives a JSON object to do all the query filtering. For a >>>> simple lookup it is has a simple structre, as the query gets more >>>> complex it gets esoteric as well (with "special" MongoDB keys in the >>>> format of "$key"). >>>> >>>> Because the simplest map we have to a JSON Object is the Dictionary, I >>>> guess that's why it ends up being converted to a Dictionary, which in >>>> turn gets converted to JSON and/or BSON. >>>> >>>> Regards, >>>> >>>> Esteban A. Maringolo >>>> >>>> >>>> 2013/7/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>>> >>>>> On Jul 4, 2013, at 2:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>> >>>>> Hi :) >>>>> >>>>> can you check if you have the "MongoQueries" package installed? >>>>> >>>>> cheers, >>>>> Esteban >>>>> >>>>> ps: please notice that in anycase you will not be able to execute >>>>> >>>>> [ :each | each name first = $X ] >>>>> >>>>> because the MongoQueries package just translates the block into a >>>>> mongo-query which is a dictionary (a JSON expression). But you will found >>>>> some ways to help you, some special keywords like #in: and #where: (you can >>>>> see how they work in the tests) >>>>> >>>>> >>>>> esteban >>>>> how a dictionary is used to work as a block for a query? >>>>> Can you explain because I would have thought that the first line did not >>>>> work and the second would work. >>>>> >>>>> Stef >>>>> >>>>> >>>>> >>>>> >>>>> On Jul 4, 2013, at 2:17 PM, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> >>>>> wrote: >>>>> >>>>> Hi! >>>>> >>>>> I realize probably only Esteban will be able to answer, but I prefer to >>>>> write to the list so the mail is logged and other people can benefit from >>>>> it. >>>>> >>>>> I'm trying to use blocks as arguments for #selectOne: and #selectMany:, but >>>>> it doesn't seem to work. Here's my code: >>>>> >>>>> MyClass selectOne: { #name -> 'Some name' } asDictionary. >>>>> MyClass selectOne: [ :each | each name = 'Some name' ]. >>>>> >>>>> >>>>> The first one works, but the second one raises a VOMongoConnectionError. >>>>> >>>>> Also: >>>>> >>>>> MyClass selectMany: { #name -> 'Some name' } asDictionary. >>>>> MyClass selectMany: [ :each | each name = 'Some name' ]. >>>>> >>>>> >>>>> The first does work, the second one doesn't, which prevents me from writing >>>>> more useful stuff like: >>>>> >>>>> MyClass selectMany: [ :each | each name first = $P ]. >>>>> >>>>> Any idea why this could be failing? I've the latest stable version loaded >>>>> via: >>>>> >>>>> Gofer it >>>>> url: 'http://smalltalkhub.com/mc/estebanlm/Voyage/main'; >>>>> package: 'ConfigurationOfVoyageMongo'; >>>>> load. >>>>> (Smalltalk at: #ConfigurationOfVoyageMongo) load. >>>>> >>>>> Thanks! :) >>>>> >>>>> Bernat. >>>>> >>>>> -- >>>>> Bernat Romagosa. >>>>> >>>>> >>>>> >>>> >>> >>> >> >> > >

July 6, 2013

Re: [Pharo-users] [Voyage] #selectOne: and #selectMany: with a block as the argument

by StÃ©phane Ducasse

Sorry but I hate this! We should be better at writing doc. I do not want to learn this because I ask in the mailing-list if you see what I mean. Now that Gutenberg is working we should use it for real It is based on github so people should be happy and it delivers pdf and html (and whatever will be needed) So please join and help us building a real system. Stef > Good to know! > > > 2013/7/4 Esteban Lorenzano <estebanlm(a)gmail.com> > you also have regexp expressions (and I think they are better than the where clause): > > { > #name -> { > '$regex' -> '^P*'. > '$options' -> 'i' > } asDictionary > } asDictionary > > there is no support for it with MongoQueries, but they work fine with dictionaries :) > > Esteban > > On Jul 4, 2013, at 7:36 PM, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > >> For other kinds of matches, you need javascript queries, if I understood: >> >> User selectOne: [ :each | each where: 'this.name[0] == "s"' ] >> >> Right? >> >> >> 2013/7/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> Ok but how do I map conceptual a query to a dictionary >> >> Do I guess right that there is an exact match >> >> selectOne: { id -> 10} asDictionary >> >> will match id = 10 >> >> Now we can only do exact mathc? >> >> name matches: 'stef*' >> >> >> On Jul 4, 2013, at 6:04 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >> > Stef, >> > >> > You're asking the other Esteban, but having used Voyage and Mongo I >> > think I can answer this. >> > >> > Mongo receives a JSON object to do all the query filtering. For a >> > simple lookup it is has a simple structre, as the query gets more >> > complex it gets esoteric as well (with "special" MongoDB keys in the >> > format of "$key"). >> > >> > Because the simplest map we have to a JSON Object is the Dictionary, I >> > guess that's why it ends up being converted to a Dictionary, which in >> > turn gets converted to JSON and/or BSON. >> > >> > Regards, >> > >> > Esteban A. Maringolo >> > >> > >> > 2013/7/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >> >> >> On Jul 4, 2013, at 2:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> >> >> Hi :) >> >> >> >> can you check if you have the "MongoQueries" package installed? >> >> >> >> cheers, >> >> Esteban >> >> >> >> ps: please notice that in anycase you will not be able to execute >> >> >> >> [ :each | each name first = $X ] >> >> >> >> because the MongoQueries package just translates the block into a >> >> mongo-query which is a dictionary (a JSON expression). But you will found >> >> some ways to help you, some special keywords like #in: and #where: (you can >> >> see how they work in the tests) >> >> >> >> >> >> esteban >> >> how a dictionary is used to work as a block for a query? >> >> Can you explain because I would have thought that the first line did not >> >> work and the second would work. >> >> >> >> Stef >> >> >> >> >> >> >> >> >> >> On Jul 4, 2013, at 2:17 PM, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> >> >> wrote: >> >> >> >> Hi! >> >> >> >> I realize probably only Esteban will be able to answer, but I prefer to >> >> write to the list so the mail is logged and other people can benefit from >> >> it. >> >> >> >> I'm trying to use blocks as arguments for #selectOne: and #selectMany:, but >> >> it doesn't seem to work. Here's my code: >> >> >> >> MyClass selectOne: { #name -> 'Some name' } asDictionary. >> >> MyClass selectOne: [ :each | each name = 'Some name' ]. >> >> >> >> >> >> The first one works, but the second one raises a VOMongoConnectionError. >> >> >> >> Also: >> >> >> >> MyClass selectMany: { #name -> 'Some name' } asDictionary. >> >> MyClass selectMany: [ :each | each name = 'Some name' ]. >> >> >> >> >> >> The first does work, the second one doesn't, which prevents me from writing >> >> more useful stuff like: >> >> >> >> MyClass selectMany: [ :each | each name first = $P ]. >> >> >> >> Any idea why this could be failing? I've the latest stable version loaded >> >> via: >> >> >> >> Gofer it >> >> url: 'http://smalltalkhub.com/mc/estebanlm/Voyage/main'; >> >> package: 'ConfigurationOfVoyageMongo'; >> >> load. >> >> (Smalltalk at: #ConfigurationOfVoyageMongo) load. >> >> >> >> Thanks! :) >> >> >> >> Bernat. >> >> >> >> -- >> >> Bernat Romagosa. >> >> >> >> >> >> >> > >> >> >> >> >> >> -- >> Bernat Romagosa. > > > > > -- > Bernat Romagosa.

July 6, 2013

Re: [Pharo-users] [Voyage] #selectOne: and #selectMany: with a block as the argument

by StÃ©phane Ducasse

esteban could you take some time to add this information to the Voyage chapter? https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ add the information in any format and I can make it run. https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english Stef On Jul 4, 2013, at 7:49 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > you have different constructions: > > { $gt: { "number_field": 42 } } > > and so on... always with dictionaries (bah, json structs). > > as a query language it kinda sucks... but well... is how it is :) > > On Jul 4, 2013, at 7:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Ok but how do I map conceptual a query to a dictionary >> >> Do I guess right that there is an exact match >> >> selectOne: { id -> 10} asDictionary >> >> will match id = 10 >> >> Now we can only do exact mathc? >> >> name matches: 'stef*' >> >> >> On Jul 4, 2013, at 6:04 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >>> Stef, >>> >>> You're asking the other Esteban, but having used Voyage and Mongo I >>> think I can answer this. >>> >>> Mongo receives a JSON object to do all the query filtering. For a >>> simple lookup it is has a simple structre, as the query gets more >>> complex it gets esoteric as well (with "special" MongoDB keys in the >>> format of "$key"). >>> >>> Because the simplest map we have to a JSON Object is the Dictionary, I >>> guess that's why it ends up being converted to a Dictionary, which in >>> turn gets converted to JSON and/or BSON. >>> >>> Regards, >>> >>> Esteban A. Maringolo >>> >>> >>> 2013/7/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> >>>> On Jul 4, 2013, at 2:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> Hi :) >>>> >>>> can you check if you have the "MongoQueries" package installed? >>>> >>>> cheers, >>>> Esteban >>>> >>>> ps: please notice that in anycase you will not be able to execute >>>> >>>> [ :each | each name first = $X ] >>>> >>>> because the MongoQueries package just translates the block into a >>>> mongo-query which is a dictionary (a JSON expression). But you will found >>>> some ways to help you, some special keywords like #in: and #where: (you can >>>> see how they work in the tests) >>>> >>>> >>>> esteban >>>> how a dictionary is used to work as a block for a query? >>>> Can you explain because I would have thought that the first line did not >>>> work and the second would work. >>>> >>>> Stef >>>> >>>> >>>> >>>> >>>> On Jul 4, 2013, at 2:17 PM, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> >>>> wrote: >>>> >>>> Hi! >>>> >>>> I realize probably only Esteban will be able to answer, but I prefer to >>>> write to the list so the mail is logged and other people can benefit from >>>> it. >>>> >>>> I'm trying to use blocks as arguments for #selectOne: and #selectMany:, but >>>> it doesn't seem to work. Here's my code: >>>> >>>> MyClass selectOne: { #name -> 'Some name' } asDictionary. >>>> MyClass selectOne: [ :each | each name = 'Some name' ]. >>>> >>>> >>>> The first one works, but the second one raises a VOMongoConnectionError. >>>> >>>> Also: >>>> >>>> MyClass selectMany: { #name -> 'Some name' } asDictionary. >>>> MyClass selectMany: [ :each | each name = 'Some name' ]. >>>> >>>> >>>> The first does work, the second one doesn't, which prevents me from writing >>>> more useful stuff like: >>>> >>>> MyClass selectMany: [ :each | each name first = $P ]. >>>> >>>> Any idea why this could be failing? I've the latest stable version loaded >>>> via: >>>> >>>> Gofer it >>>> url: 'http://smalltalkhub.com/mc/estebanlm/Voyage/main'; >>>> package: 'ConfigurationOfVoyageMongo'; >>>> load. >>>> (Smalltalk at: #ConfigurationOfVoyageMongo) load. >>>> >>>> Thanks! :) >>>> >>>> Bernat. >>>> >>>> -- >>>> Bernat Romagosa. >>>> >>>> >>>> >>> >> >> > >

July 6, 2013

Re: [Pharo-users] documentation for refactoring tools in Pharo 2

by Damien Cassou

On Thu, Jul 4, 2013 at 5:11 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Camillo and I deteremined that its probably a Nautilus bug that prevents > the "Code Rewriting" tools from working in Pharo 2 (I'm using 20606) > from within the browser (see > > http://forum.world.st/how-to-use-RBClassRegexRefactoring-in-Pharo-2-td46957… > ). > But in 1.4 you could use Omnibrowser & the Code rewriting tools. > the issue for Pharo 3.0 is https://pharo.fogbugz.com/default.asp?7215. Feel free to backport the change to 2.0. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 5, 2013

Re: [Pharo-users] Regex question

by jannik laval

Yes it is. I will update the chapter on Regex. Thank you Camillo Jannik 2013/7/5 Camillo Bruni <camillobruni(a)gmail.com> > I think that is highly implementation dependent. I guess in this case the > Regex matches multilines? > > On 2013-07-05, at 07:51, "jannik.laval" <jannik.laval(a)gmail.com> wrote: > > Yes, now in the chapter on Regex, it is written that '.' matches only a > single character except cr. > > > > So, the command "String cr matchesRegex: '.'" should return false in > this case. > > But since at least Pharo1.3 (I don't try previous version), it returns > true. > > > > Jannik > > > > > > > > On Jul 5, 2013, at 12:33 AM, Camillo Bruni <camillobruni(a)gmail.com> > wrote: > > > >> Yes this is ok, '.' matches only a single character. > >> The alternatives you might be looking for are #prefixMatchesRegex: or > '.*' > >> > >> On 2013-07-05, at 00:03, "jannik.laval" <jannik.laval(a)gmail.com> wrote: > >>> Hi guys, > >>> > >>> Just a simple question about regex: > >>> > >>> 'a' matchesRegex: '.' --> true > >>> 'aa' matchesRegex: '.' --> false > >>> > >>> As '.' represents any character, the two previous lines are ok. Now, > if I test with a cr, it returns true: > >>> > >>> String cr matchesRegex: '.' --> true. > >>> > >>> Is it the expected behavior ? > >>> > >>> Cheers, > >>> Jannik > >> > >> > > > > > > > -- ~~Dr. Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu

July 5, 2013

Re: [Pharo-users] Regex question

by Camillo Bruni

I think that is highly implementation dependent. I guess in this case the Regex matches multilines? On 2013-07-05, at 07:51, "jannik.laval" <jannik.laval(a)gmail.com> wrote: > Yes, now in the chapter on Regex, it is written that '.' matches only a single character except cr. > > So, the command "String cr matchesRegex: '.'" should return false in this case. > But since at least Pharo1.3 (I don't try previous version), it returns true. > > Jannik > > > > On Jul 5, 2013, at 12:33 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> Yes this is ok, '.' matches only a single character. >> The alternatives you might be looking for are #prefixMatchesRegex: or '.*' >> >> On 2013-07-05, at 00:03, "jannik.laval" <jannik.laval(a)gmail.com> wrote: >>> Hi guys, >>> >>> Just a simple question about regex: >>> >>> 'a' matchesRegex: '.' --> true >>> 'aa' matchesRegex: '.' --> false >>> >>> As '.' represents any character, the two previous lines are ok. Now, if I test with a cr, it returns true: >>> >>> String cr matchesRegex: '.' --> true. >>> >>> Is it the expected behavior ? >>> >>> Cheers, >>> Jannik >> >> > >

July 5, 2013

We need you for a software integration survey (reminder)

by Martin Dias

Hi all, Some time ago we sent an email to ask you contributing to a research to improve tools for software integration. If you maintain a project with multiple contributors, we will greatly appreciate your participation. Your answers will be used for research purposes and to support the development of new tools. You can later access the results of this study, make free use of our tools to support the integration of changes, and maybe receive a gift. We found out that the survey was not properly working on Safari (and may be also some other browsers). And we have now corrected this issue. Up to now, we received 36 full answers and 166 incomplete answers. So we decided to give you an extra month, if you started to fill the survey, please consider resuming filling the survey. For this you only need to go back to the same site: https://sondages.inria.fr/index.php/667625/lang-en If you did not yet fill in the survey, please consider doing it now. Best regards, Martin Dias, Nicolas Anquetil, Veronica Isabel Uquillas, StÃ©phane Ducasse and the RMOD Inria team

July 5, 2013

Re: [Pharo-users] Regex question

by jannik.laval

Yes, now in the chapter on Regex, it is written that '.' matches only a single character except cr. So, the command "String cr matchesRegex: '.'" should return false in this case. But since at least Pharo1.3 (I don't try previous version), it returns true. Jannik On Jul 5, 2013, at 12:33 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > Yes this is ok, '.' matches only a single character. > The alternatives you might be looking for are #prefixMatchesRegex: or '.*' > > On 2013-07-05, at 00:03, "jannik.laval" <jannik.laval(a)gmail.com> wrote: >> Hi guys, >> >> Just a simple question about regex: >> >> 'a' matchesRegex: '.' --> true >> 'aa' matchesRegex: '.' --> false >> >> As '.' represents any character, the two previous lines are ok. Now, if I test with a cr, it returns true: >> >> String cr matchesRegex: '.' --> true. >> >> Is it the expected behavior ? >> >> Cheers, >> Jannik > >

July 5, 2013

Re: [Pharo-users] Pharo on Fedora 19

by Daniel Miranda

Libraries reinstaller, problem persists, Pharo is definitely stuck on findMethodWithPrimitiveFromContextUpToContext(). It looks like a problem during initialization, way before graphics drivers would get in the way. As I mentioned the 3.0 alpha runs OK, which further raises my suspicions of a VM bug (what would be special about my system to cause is a more complex matter). Daniel On Thu, Jul 4, 2013 at 11:22 PM, danielkza <danielkza2(a)gmail.com> wrote: > I'll try reinstalling the libraries as instructed. I'm currently using the > latest proprietary NVIDIA drivers, they may the problem. I suspect not > because I tried the 3.0 alpha and it ran fine. > > > > -- > View this message in context: > http://forum.world.st/Pharo-on-Fedora-19-tp4697358p4697455.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

July 5, 2013