[Moose-dev] Re: retrieve 'Memory class' in CAnalyzer

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 &lt;alexandre(a)bergel.eu&gt; 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 &lt;cy.delaunay(a)gmail.com&gt; Ok, let's see :) 2010/1/25 Alexandre Bergel &lt;alexandre(a)bergel.eu&gt; 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 Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- Simon _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev