[Moose-dev] retrieve 'Memory class' in CAnalyzer
Locked
 
|
Hello,
A thing it would be cool to retrieve from C code for a function, is the thing called 'Memory class'. It is the word prefixing a function declaration: - global - local
- static - extern - register I have looked at a xml file generated with srcml and a function is declared like that: <function><type><name>static</name> <name>void</name></type> ... So it seems to be quite simple to retrieve, what do you think ?
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
[Moose-dev] Re: retrieve 'Memory class' in CAnalyzer
|
|
On 25 janv. 2010, at 10:19, Cyrille Delaunay wrote: > Hello, > > A thing it would be cool to retrieve from C code for a function, is the thing called 'Memory class'. It is the word prefixing a function declaration: > - global > - local > - static > - extern > - register > > I have looked at a xml file generated with srcml and a function is declared like that: > <function><type><name>static</name> <name>void</name></type> ... yep, that would be good. > > So it seems to be quite simple to retrieve, what do you think ? > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- Simon _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
[Moose-dev] Re: retrieve 'Memory class' in CAnalyzer
|
|
In reply to this post by cdelaunay
Yes Cyrille, it would be great.
Do you want to give a try? Let us know when done. I will review the code. Do not forget unit tests :-) Cheers, Alexandre On 25 Jan 2010, at 06:19, Cyrille Delaunay wrote: > Hello, > > A thing it would be cool to retrieve from C code for a function, is > the thing called 'Memory class'. It is the word prefixing a function > declaration: > - global > - local > - static > - extern > - register > > I have looked at a xml file generated with srcml and a function is > declared like that: > <function><type><name>static</name> <name>void</name></ > type> ... > > So it seems to be quite simple to retrieve, what do you think ? > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Ok, let's see :)
2010/1/25 Alexandre Bergel <[hidden email]> Yes Cyrille, it would be great. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
[Moose-dev] ConfigurationOfGlamour: Glamour and Mondrian decoupling
|
|
Tudor i think ConfigurationOfGlamour should provide groups for decoupling Glamour installation and Mondrian installation.
Not everybody using scriptable browsers want to use Mondrian panes. In summary, In the default group leave out Mondrian packages dependencies and provide a metacello group for loading Glamour+Mondrian explicitly. Pros: Faster installation time and decoupling Glamour from Mondrian. Cons: people not familiar with Metacello could get puzzled, but for this you could provide convenience method in ConfigurationOfGlamour class ( like we did in ConfigurationOfAlien). What do you think? Fernando pd: In the method you provide some groups already. baseline20beta3: spec ... spec group: 'Tests' with: #( 'Glamour-Tests' 'Glamour-Examples' 'Glamour-Test-Morphic'). .... _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by cdelaunay
Memory Class apply on Function but also on variables. The common class for both type is FAMIXNamedEntity. Is it a good idea to define an instance variable 'memoryClass' in this class ?
2010/1/25 Cyrille Delaunay <[hidden email]> Ok, let's see :) _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
[Moose-dev] Re: retrieve 'Memory class' in CAnalyzer
|
|
I am not a FAMIX expert, but I would create class extensions on
FAMIXNamedEntity and use properties to store the memory class. Providing tests are key here, if we need to change the implementation later on. Alexandre On 25 Jan 2010, at 10:11, Cyrille Delaunay wrote: > Memory Class apply on Function but also on variables. The common > class for both type is FAMIXNamedEntity. Is it a good idea to define > an instance variable 'memoryClass' in this class ? > > 2010/1/25 Cyrille Delaunay <[hidden email]> > Ok, let's see :) > > 2010/1/25 Alexandre Bergel <[hidden email]> > > Yes Cyrille, it would be great. > Do you want to give a try? Let us know when done. I will review the > code. > Do not forget unit tests :-) > > Cheers, > Alexandre > > > On 25 Jan 2010, at 06:19, Cyrille Delaunay wrote: > > Hello, > > A thing it would be cool to retrieve from C code for a function, is > the thing called 'Memory class'. It is the word prefixing a function > declaration: > - global > - local > - static > - extern > - register > > I have looked at a xml file generated with srcml and a function is > declared like that: > <function><type><name>static</name> <name>void</name></ > type> ... > > So it seems to be quite simple to retrieve, what do you think ? > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
[Moose-dev] Re: retrieve 'Memory class' in CAnalyzer
|
|
In reply to this post by cdelaunay
On 25 janv. 2010, at 14:11, Cyrille Delaunay wrote: Memory Class apply on Function but also on variables. The common class for both type is FAMIXNamedEntity. Is it a good idea to define an instance variable 'memoryClass' in this class ? Use the extension mechanism of MooseEntity for state. See MooseEntity>>privateState and EntityState class
-- Simon _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
[Moose-dev] Re: retrieve 'Memory class' in CAnalyzer
|
|
Yeah, this is what I meant.
Alexandre On 25 Jan 2010, at 10:41, Simon Denier wrote: > > On 25 janv. 2010, at 14:11, Cyrille Delaunay wrote: > >> Memory Class apply on Function but also on variables. The common >> class for both type is FAMIXNamedEntity. Is it a good idea to >> define an instance variable 'memoryClass' in this class ? > > > Use the extension mechanism of MooseEntity for state. > > See MooseEntity>>privateState and EntityState class > > >> >> 2010/1/25 Cyrille Delaunay <[hidden email]> >> Ok, let's see :) >> >> 2010/1/25 Alexandre Bergel <[hidden email]> >> >> Yes Cyrille, it would be great. >> Do you want to give a try? Let us know when done. I will review the >> code. >> Do not forget unit tests :-) >> >> Cheers, >> Alexandre >> >> >> On 25 Jan 2010, at 06:19, Cyrille Delaunay wrote: >> >> Hello, >> >> A thing it would be cool to retrieve from C code for a function, is >> the thing called 'Memory class'. It is the word prefixing a >> function declaration: >> - global >> - local >> - static >> - extern >> - register >> >> I have looked at a xml file generated with srcml and a function is >> declared like that: >> <function><type><name>static</name> <name>void</name></ >> type> ... >> >> So it seems to be quite simple to retrieve, what do you think ? >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > Simon > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
This is done. Note that the common name is 'StorageClass' and not 'MemoryClass' like I said.
For the moment, if a specific storageClass is specified before a function (#static or #extern ) or a variable (#static #extern #register or #auto), it will retrieve and store it. It will help me to do what I want now.
But I should complete it: -> if no class is specified, store the default one. Documentation on the web is saying a lot of different things, but I think for both (functions and variables), the default storageClass is #global
-> what about other kind of entities. What is involved if I have " typedef static ..... ". I have written some tests.
2010/1/25 Alexandre Bergel <[hidden email]> Yeah, this is what I meant. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
[Moose-dev] Re: retrieve 'Memory class' in CAnalyzer
|
|
Ok, I will try in a few minutes. I am loading the whole stuff now...
Alexandre On 25 Jan 2010, at 13:05, Cyrille Delaunay wrote: > This is done. Note that the common name is 'StorageClass' and not > 'MemoryClass' like I said. > For the moment, if a specific storageClass is specified before a > function (#static or #extern ) or a variable (#static #extern > #register or #auto), it will retrieve and store it. It will help me > to do what I want now. > But I should complete it: > -> if no class is specified, store the default one. Documentation on > the web is saying a lot of different things, but I think for both > (functions and variables), the default storageClass is #global > -> what about other kind of entities. What is involved if I have " > typedef static ..... ". > > I have written some tests. > > 2010/1/25 Alexandre Bergel <[hidden email]> > Yeah, this is what I meant. > > Alexandre > > > On 25 Jan 2010, at 10:41, Simon Denier wrote: > > > On 25 janv. 2010, at 14:11, Cyrille Delaunay wrote: > > Memory Class apply on Function but also on variables. The common > class for both type is FAMIXNamedEntity. Is it a good idea to define > an instance variable 'memoryClass' in this class ? > > > Use the extension mechanism of MooseEntity for state. > > See MooseEntity>>privateState and EntityState class > > > > 2010/1/25 Cyrille Delaunay <[hidden email]> > Ok, let's see :) > > 2010/1/25 Alexandre Bergel <[hidden email]> > > Yes Cyrille, it would be great. > Do you want to give a try? Let us know when done. I will review the > code. > Do not forget unit tests :-) > > Cheers, > Alexandre > > > On 25 Jan 2010, at 06:19, Cyrille Delaunay wrote: > > Hello, > > A thing it would be cool to retrieve from C code for a function, is > the thing called 'Memory class'. It is the word prefixing a function > declaration: > - global > - local > - static > - extern > - register > > I have looked at a xml file generated with srcml and a function is > declared like that: > <function><type><name>static</name> <name>void</name></ > type> ... > > So it seems to be quite simple to retrieve, what do you think ? > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > Simon > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
[Moose-dev] Re: retrieve 'Memory class' in CAnalyzer
|
|
In reply to this post by cdelaunay
would you mind renaming it
storageKind ? because class is confusing in Smalltalk we will always think that this is a constructor. Stef On Jan 25, 2010, at 5:05 PM, Cyrille Delaunay wrote: > This is done. Note that the common name is 'StorageClass' and not 'MemoryClass' like I said. > For the moment, if a specific storageClass is specified before a function (#static or #extern ) or a variable (#static #extern #register or #auto), it will retrieve and store it. It will help me to do what I want now. > But I should complete it: > -> if no class is specified, store the default one. Documentation on the web is saying a lot of different things, but I think for both (functions and variables), the default storageClass is #global > -> what about other kind of entities. What is involved if I have " typedef static ..... ". > > I have written some tests. > > 2010/1/25 Alexandre Bergel <[hidden email]> > Yeah, this is what I meant. > > Alexandre > > > On 25 Jan 2010, at 10:41, Simon Denier wrote: > > > On 25 janv. 2010, at 14:11, Cyrille Delaunay wrote: > > Memory Class apply on Function but also on variables. The common class for both type is FAMIXNamedEntity. Is it a good idea to define an instance variable 'memoryClass' in this class ? > > > Use the extension mechanism of MooseEntity for state. > > See MooseEntity>>privateState and EntityState class > > > > 2010/1/25 Cyrille Delaunay <[hidden email]> > Ok, let's see :) > > 2010/1/25 Alexandre Bergel <[hidden email]> > > Yes Cyrille, it would be great. > Do you want to give a try? Let us know when done. I will review the code. > Do not forget unit tests :-) > > Cheers, > Alexandre > > > On 25 Jan 2010, at 06:19, Cyrille Delaunay wrote: > > Hello, > > A thing it would be cool to retrieve from C code for a function, is the thing called 'Memory class'. It is the word prefixing a function declaration: > - global > - local > - static > - extern > - register > > I have looked at a xml file generated with srcml and a function is declared like that: > <function><type><name>static</name> <name>void</name></type> ... > > So it seems to be quite simple to retrieve, what do you think ? > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > Simon > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
[Moose-dev] Re: retrieve 'Memory class' in CAnalyzer
|
|
In reply to this post by cdelaunay
I checked what you did. #testFunctionStorageClass looks really good!
Alexandre On 25 Jan 2010, at 13:05, Cyrille Delaunay wrote: > This is done. Note that the common name is 'StorageClass' and not > 'MemoryClass' like I said. > For the moment, if a specific storageClass is specified before a > function (#static or #extern ) or a variable (#static #extern > #register or #auto), it will retrieve and store it. It will help me > to do what I want now. > But I should complete it: > -> if no class is specified, store the default one. Documentation on > the web is saying a lot of different things, but I think for both > (functions and variables), the default storageClass is #global > -> what about other kind of entities. What is involved if I have " > typedef static ..... ". > > I have written some tests. > > 2010/1/25 Alexandre Bergel <[hidden email]> > Yeah, this is what I meant. > > Alexandre > > > On 25 Jan 2010, at 10:41, Simon Denier wrote: > > > On 25 janv. 2010, at 14:11, Cyrille Delaunay wrote: > > Memory Class apply on Function but also on variables. The common > class for both type is FAMIXNamedEntity. Is it a good idea to define > an instance variable 'memoryClass' in this class ? > > > Use the extension mechanism of MooseEntity for state. > > See MooseEntity>>privateState and EntityState class > > > > 2010/1/25 Cyrille Delaunay <[hidden email]> > Ok, let's see :) > > 2010/1/25 Alexandre Bergel <[hidden email]> > > Yes Cyrille, it would be great. > Do you want to give a try? Let us know when done. I will review the > code. > Do not forget unit tests :-) > > Cheers, > Alexandre > > > On 25 Jan 2010, at 06:19, Cyrille Delaunay wrote: > > Hello, > > A thing it would be cool to retrieve from C code for a function, is > the thing called 'Memory class'. It is the word prefixing a function > declaration: > - global > - local > - static > - extern > - register > > I have looked at a xml file generated with srcml and a function is > declared like that: > <function><type><name>static</name> <name>void</name></ > type> ... > > So it seems to be quite simple to retrieve, what do you think ? > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > Simon > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
[Moose-dev] Re: ConfigurationOfGlamour: Glamour and Mondrian decoupling
|
|
In reply to this post by Fernando olivero
Hi Fernando,
That is not a bad idea, but it will probably take a while until I do it because it also implies repackaging :). Cheers, Doru On 25 Jan 2010, at 13:36, Fernando olivero wrote: > Tudor i think ConfigurationOfGlamour should provide groups for > decoupling Glamour installation and Mondrian installation. > > Not everybody using scriptable browsers want to use Mondrian panes. > > In summary, In the default group leave out Mondrian packages > dependencies and provide a metacello group for loading Glamour > +Mondrian explicitly. > > Pros: Faster installation time and decoupling Glamour from Mondrian. > > Cons: people not familiar with Metacello could get puzzled, but for > this you could provide convenience method in ConfigurationOfGlamour > class ( like we did in ConfigurationOfAlien). > > > What do you think? > > Fernando > > > > pd: In the method you provide some groups already. > > baseline20beta3: spec > ... > spec group: 'Tests' with: #( > 'Glamour-Tests' > 'Glamour-Examples' > 'Glamour-Test-Morphic'). > .... > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
[Moose-dev] Re: ConfigurationOfGlamour: Glamour and Mondrian decoupling
|
|
Hi,
I created an issue: http://code.google.com/p/moose-technology/issues/detail?id=310 Cheers, Doru On 26 Jan 2010, at 09:12, Tudor Girba wrote: > Hi Fernando, > > That is not a bad idea, but it will probably take a while until I do > it because it also implies repackaging :). > > Cheers, > Doru > > > On 25 Jan 2010, at 13:36, Fernando olivero wrote: > >> Tudor i think ConfigurationOfGlamour should provide groups for >> decoupling Glamour installation and Mondrian installation. >> >> Not everybody using scriptable browsers want to use Mondrian panes. >> >> In summary, In the default group leave out Mondrian packages >> dependencies and provide a metacello group for loading Glamour >> +Mondrian explicitly. >> >> Pros: Faster installation time and decoupling Glamour from >> Mondrian. >> >> Cons: people not familiar with Metacello could get puzzled, but for >> this you could provide convenience method in >> ConfigurationOfGlamour class ( like we did in ConfigurationOfAlien). >> >> >> What do you think? >> >> Fernando >> >> >> >> pd: In the method you provide some groups already. >> >> baseline20beta3: spec >> ... >> spec group: 'Tests' with: #( >> 'Glamour-Tests' >> 'Glamour-Examples' >> 'Glamour-Test-Morphic'). >> .... >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "If you interrupt the barber while he is cutting your hair, > you will end up with a messy haircut." > -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |