From: Baptiste L. <gai...@fr...> - 2002-12-15 20:24:08
|
Well, the subject said it all. Please, notes that I removed ScopeGeneratorTest and ScopesHolderTest from the Makefile. Andre, you can see the file related to the 'if' condition by looking for '* added declaration in condition parsing' in the log (I recommend using sourceforge cvs web interface for this). The ScopeGenerator and ScopesHolder test will be removed soon. I'm done with testing the new IdentifierResolver. I'm tackling the unit tests for IdentifierResolverContext (which manages local variables visibility). Baptiste. |
From: Andre B. <and...@gm...> - 2002-12-16 20:29:11
|
What about adding me to the developer list and assign the first todo item to me ? Well, i hope this item "Add parsing for 'for' statement condition declaration, The resulting AST structure should look like ...." could be solvable for me. Just send me a message - I will start. Anyway I still continue looking at the sources and trying to understand the data flow ... :-) Baptiste Lepilleur wrote: > Well, the subject said it all. Please, notes that I removed >ScopeGeneratorTest and ScopesHolderTest from the Makefile. > > Andre, you can see the file related to the 'if' condition by looking for >'* added declaration in condition parsing' in the log (I recommend using >sourceforge cvs web interface for this). > I will. However I got now work my WinCVS together with WinMerge. See, ya André Baresel |
From: Baptiste L. <gai...@fr...> - 2002-12-16 22:14:39
|
----- Original Message ----- From: "Andre Baresel" <and...@gm...> To: "CppTool Mailing List" <Cpp...@li...> Sent: Monday, December 16, 2002 9:26 PM Subject: [Cpptool-develop] what about another developer ? > What about adding me to the developer list and assign the first todo > item to me ? Your welcome Andre, though you'll have to wait for Sven to do it as I don't have admin right. Task are self-assigned. Just edit the wiki Todo page and change the status to 'In Progress' and put your name beside it. Also, send a mail to the ML so people are notified. > Well, i hope this item "Add parsing for 'for' statement condition > declaration, The resulting AST structure should look like ...." > could be solvable for me. If you managed to do the 'if condition', it should not be to difficult. Let us know if you have any issues. Baptiste. [...] > > See, ya > André Baresel |
From: Sven R. <rei...@ma...> - 2002-12-17 15:31:33
|
On Mon, 16 Dec 2002, Baptiste Lepilleur wrote: > ----- Original Message ----- > From: "Andre Baresel" <and...@gm...> > > What about adding me to the developer list and assign the first todo > > item to me ? > > Your welcome Andre, though you'll have to wait for Sven to do it as I don't > have admin right. I should have done that before, and I'm trying to do it now. However, the SF server appears to have some problems right now (see message about ML archives). I'll let you know when I succeed. Sven. -- Sven Reichard Dept. of Math. Sci. University of Delaware rei...@ma... |
From: Baptiste L. <gai...@fr...> - 2002-12-16 22:36:01
|
----- Original Message ----- From: "Baptiste Lepilleur" <gai...@fr...> To: "CppTool Mailing List" <Cpp...@li...> Sent: Sunday, December 15, 2002 9:19 PM Subject: [Cpptool-develop] Added declaration parsing in condition of if, while, and switch statement. > Well, the subject said it all. Please, notes that I removed > ScopeGeneratorTest and ScopesHolderTest from the Makefile. > [...] > The ScopeGenerator and ScopesHolder test will be removed soon. I'm done > with testing the new IdentifierResolver. I'm tackling the unit tests for > IdentifierResolverContext (which manages local variables visibility). Well, I'm finally did it. All the Scope* classes were removed and the code now use the new IdentifierResolver and IdentifierResolverContext. Once again the classes are miss-named :-(. IdentifierResolverContext should be named IdentifierResolver. I would have go ahead and renamed them, but I can't find a name for the current IdentifierResolver class. Suggestion are welcome. IdentifierResolver and IdentifierResolverStrategy are probably a for of the Director/Builder pattern. IdentifierResolver does the analysis (entry/exit scope, local variable declaration...), while IdentifierResolverStrategy process those 'event'. IdentifierResolverContext is a specialization of IdentifierResolverStrategy. I expect a few change to come up when we add a specialization of IdentifierResolverStrategy to detect if it is valid to declare a new locale variable at a given location (e.g. the identifier is not used in the scope), and when ReduceTemporary scope is implemented. Also, it should be fairly easy to extend IdentifierResolverContext to handle class attributes and methods. For now, I'll go back to working on the VC6 add-ins (mainly need to add a generique fixture to test TextDocument interface). Baptiste. > Baptiste. |
From: Andre B. <and...@gm...> - 2002-12-17 11:34:56
|
Hello Baptiste, don't bother about the "stdafx.h" problem, I think I was only stumbling accross this since I never used CVS and WinCVS before. But now I just got my own CVS-Server working at home. Just to synchronize the files of my own projects with my laptop --- works fine after I solved the authorization problems. Since we heavily use another CVS system at work which is a little bit more comfortable to install and run (but to expensive for private use), it was somehow difficult to find out how the the actions are named in CVS/WinCVS but after all I found nearly all needed for adding/ checking /updating files and directories. Btw) Is there any possibility to move files that are allready in the repository from one directory to another and this ofcourse together with all versions that are in the repository ? Did I miss this action in the CVS or isn't there such an operation ? I found this very usefull for restructuring the code some time >IdentifierResolver and IdentifierResolverStrategy are probably a for of the >Director/Builder pattern. >IdentifierResolver does the analysis (entry/exit scope, local variable >declaration...), while IdentifierResolverStrategy process those 'event'. >IdentifierResolverContext is a specialization of IdentifierResolverStrategy. > > I wonder if you know about a good book or websides in the area of programming patterns, I ordered some at my company but well, they weren't very useful. >For now, I'll go back to working on the VC6 add-ins (mainly need to add a >generique fixture to test TextDocument interface). > > Nice ! As sven allready wrote - nothing is as good as test with the real world environment 8-) see you than. -- Andre |
From: Baptiste L. <gai...@fr...> - 2002-12-17 15:53:06
|
Quoting Andre Baresel <and...@gm...>: > Hello Baptiste, > > don't bother about the "stdafx.h" problem, I think I was only stumbling > > accross this since > I never used CVS and WinCVS before. But now I just got my own CVS-Server > > working > at home. Just to synchronize the files of my own projects with my laptop I do also have a conflict for stdafx.h whenever I update. [...] > the the actions are named in CVS/WinCVS but after all I found nearly all > needed for > adding/ checking /updating files and directories. Btw) Is there any > possibility to move files > that are allready in the repository from one directory to another and > this ofcourse together with > all versions that are in the repository ? Did I miss this action in the > CVS or isn't there such > an operation ? I found this very usefull for restructuring the code some > time Unfortunately, there is no such operation in CVS. File moving or renaming is not supported. Just add the new file and remove the old one from the repository. This is fairly easy to do using WinCVS filters (show unknown files and show missing files). [...] > I wonder if you know about a good book or websides in the area of > programming patterns, > I ordered some at my company but well, they weren't very useful. > >For now, I'll go back to working on the VC6 add-ins (mainly need to add > a > >generique fixture to test TextDocument interface). Well, I don't know of any good book about pattern. Though concerning pattern, http://c2.com is the web site of reference. On the other hand, there is some good website concerning OO design: - Design Principle articles from Robert Martin ( http://www.objectmentor.com/resources/listArticles?key=topic&topic=Design%20Principles) - Design up (french), which give a good synthesis of those articles and relate them to patterns) http://www.design-up.com/ Baptiste. [...] > -- Andre --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/index.html Language: English, French |