Hi,
i got a strange error from the debugger: when the debug window appear (in my case because a test fail) i click on the method that i want to visualize and and another debug window appear saying "MessageNotUnderstood: TextMorphEditor>>blinkParen". Attached the log.
Than i figure out that in the last build of Moose you cannot even open a workspace because you get the same error. Seems something starting from shout but i'm not sure.
Cheers,
Fabrizio
I am baffled... I want to turn 'I am not yet watching' into
'IAmNotYetWatching'.
I got really close with:
| word additionalWord parser |
word := #word asParser plus flatten ==> [ :s | s capitalized ].
additionalWord := #space asParser, word ==> [ :n | n second ].
parser := (word, additionalWord star).
parser parse: 'I am not yet watching'.
Result: #('I' #('Am' 'Not' 'Yet' 'Watching'))
So I thought, "cool, just flatten that puppy and"... not even close! I got
the exact input string back! What?!
... same as above with flatten added \/
parser := (word, additionalWord star) flatten.
parser parse: 'I am not yet watching'.
Result: 'I am not yet watching'
Where did my capitals go and how did the spaces get back in there?
Thanks.
Sean
--
View this message in context: http://forum.world.st/PetitParser-The-Great-Flatten-Mystery-tp3072095p30720…
Sent from the Moose mailing list archive at Nabble.com.
Hi Alex,
I see that you are working on the Moose release. That is great!
Just a note: The ConfigurationOfPetitParser should remain in the repository of Lukas, and not in the repository of Moose. Could you take care of that?
Cheers,
Doru
--
www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
Why not depend on it?
I think that if we are not using Nile, all the nice work goes away. Are there any problems related to it?
Cheers,
Doru
On 3 Dec 2010, at 16:03, Alexandre Bergel wrote:
> Hi!
>
> testFlatCollectArray uses flatCollect:, which itself uses nsWriteStream.
> Is this really necessary to have Nile for this flatCollect:? Mondrian loads CollectionExtension. Is there a particular reason for this? I would rather prefer not to depend on CollectionExtension in that case...
>
> testFlatCollectArray
> "self debug: #testFlatCollectArray"
>
> self assert: ((#((1 2) (3 4) (5 3)) flatCollect: [ :each | each ] as: Array ) = #(1 2 3 4 5 3)).
> ...
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
--
www.tudorgirba.com
"In a world where everything is moving ever faster,
one might have better chances to win by moving slower."
Hi Simon,
I would suggest registering to the mailing list and asking more specific questions:
http://www.moosetechnology.org/about/contact
I would suggest scheming through the online Moose Book. In particular I would suggest to start from the last chapter:
http://www.themoosebook.org/book/philosophy
Regarding the use of Smalltalk, here is a short explanation:
http://www.themoosebook.org/book/introduction/smalltalk
Cheers,
Tudor
On 1 Dec 2010, at 17:06, (s) Simon Pakijavan wrote:
> Hi Tudor
>
> Thanks for the reply.
>
> I'm really interested in finding out what makes Moose such a usefull tool for data management and also why it is Smalltalk based. I suppose these topics would be the goal of the report. If you have any more information that may help me find the answers to these questions would be very usefull.
>
> Thank you
>
> Simon Pakijavan
> ________________________________________
> From: Tudor Girba [tudor.girba(a)gmail.com]
> Sent: 01 December 2010 02:18
> To: (s) Simon Pakijavan
> Cc: Moose-related development
> Subject: Re: [Moose-dev] Question for student report
>
> Hi Simon,
>
> I think you did not get this mail.
>
> Cheers,
> Doru
>
>
> On 30 Nov 2010, at 14:11, Tudor Girba wrote:
>
>> Hi Simon,
>>
>> Nice to hear from you.
>>
>> I am currently working with two companies that are using Moose:
>> - MCS Parametrix AG, Switzerland (http://www.parametrix.ch) - is using the latest Moose for analyzing systems written in Java and in a custom domain specific language.
>> - MMA France (http://www.mma.fr) - is using the Moose 3.2 in VW to analyze Smalltalk systems.
>>
>> Could you tell us more about the goal of the report?
>>
>> Cheers,
>> Tudor
>>
>>
>> On 30 Nov 2010, at 12:56, (s) Simon Pakijavan wrote:
>>
>>> Hello
>>>
>>> My name is Simon Pakijavan and I am a 3rd year computer science student in the UK writing a report into the applications of Moose.
>>>
>>> For my report, it would be useful to research into some of the organisations that use Moose. If you could provide me with the names of some of these organisations, I would be immensely grateful.
>>>
>>> Yours
>>>
>>> Simon Pakijavan
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> www.tudorgirba.com
>>
>> "It's not what we do that matters most, it's how we do it."
>>
>
> --
> www.tudorgirba.com
>
> "Next time you see your life passing by, say 'hi' and get to know her."
>
>
>
--
www.tudorgirba.com
"Relationships are of two kinds: those we choose and those that happen. They both matter."
Hello
My name is Simon Pakijavan and I am a 3rd year computer science student in the UK writing a report into the applications of Moose.
For my report, it would be useful to research into some of the organisations that use Moose. If you could provide me with the names of some of these organisations, I would be immensely grateful.
Yours
Simon Pakijavan
Hi!
Just to let you know that I've been working on a debug command for Mondrian. It opens a visualization that shows you how your view is structured.
Consider the visualization:
Here is the debugging visualization.
Red square are not that are cached with a bitmap. Inner nodes are the presence of a metric cache.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
i cannot find anymore OPAX under XML-Parser. After the long discussion about the future of OPAX i guess that at the end OPAX has been move, but where? I cannot see any package related to OPAX into the XML-Support repo. Where i can find the last version of the OPAX packages that have been moved from XML-Parser?
Cheers,
Fabrizio
Hi Lukas,
I noticed that you override two times the changes I pushed in the PPCompositeTest, and as expected, these changes break most of the external tests :).
In particular, there are two things that I found useful:
- the result instance variable holding the side effect of executing #parse:rule:. This is useful for reusing the grammar tests in the parser tests.
- the fail:rule: method for negative tests.
In the last comment, you mentioned that this was due to incompatibilities with Helvetia. Should we create a new class with these utilities?
Cheers,
Doru
--
www.tudorgirba.com
"When people care, great things can happen."
