Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - andymc73

Pages: [1]
1
Suggestions and Requests / Re: Request support for Doxygen Comments
« on: October 07, 2007, 08:30:29 pm »
I set up my code engineering to forward engineer only, and that C++ comments get replaced. Basically I took the Doxygen template from the Wiki and made it work how I wanted after a lot of head bashing

This implies the following:

* All element documentation goes in the model
* For extra doco, put the inline Doxygen comment after the curly brace at the start of the C++ method, so it doesnt get clobbered in the forward engineering

Pros:

- I can add non-core variables and methods to my C++ classes in the code without cluttering the model
- Core variables and methods are documented in the model and the Doxygen (we have tools that scan the XMI to report which items are undocumented)

Cons:

- Renaming a method or member leaves the old method in the C++
- ordering generally doesnt stay nice and neat in the generated source
- It cant update the FILE header comment, only class and method
- it cant do Doxygen comments on the line before member fields, they have to be inline after ( the ///< style) because the Code generator otherwise gets very badly confused

It would be much nicer if the synchronizer worked properly though...

HTH

2
Thanks all,

Ill raise a bug with registered support.


--Andrew

3
Does anyone have an opinion on this or is it just me? ??? :-[

4
Suggestions and Requests / Suggestion: bulk change filename for code gen
« on: February 18, 2007, 04:15:55 pm »
Hi all,

I often need to generate IDL code (using the MDG Corba plugin).

When using the Auto Generate files checkbox, each and every class, interface and enumeration in a package goes into its own IDL file, even though they all share the same Corba module in the generated code. However I would like to send all generated IDL for a package into a single .idl file.

My existing workaround:
If I don't check "Auto Generate", I am prompted one at a time, for every one of these elements for a target file, at which point I can select the same filename and end up with all elements in the one file.  
However this is very laborious when there are a lot of elements, and a royal ??? :-( if I want to change a filename.

Given the dialog box appears to be common for all languages I would assume the problem exists for C++ although often good coding practice would suggest that generally there would be a separate H file per class.

I note that when generating SQL DDL, however, I have the option to send all tables to one file.

I would like to see the ability to optionally (not by default) see all generated code go to the same file, without having to manually set the file one at a time after resetting code generation settings for the package.
(The equivalent setting for DDL generation is the radio button "Single File")

--Andrew

5
General Board / Re: Problem with MDA transform double quotes
« on: May 16, 2007, 09:35:36 pm »
That works really well

Thank you! :D

6
General Board / Problem with MDA transform double quotes
« on: May 09, 2007, 05:23:23 pm »
Hi

I have a class with notes like:

  This is "something"

When I try an MDA transform on it, the transform fails.  The exact error varies but it is usually of the form:

  Unexpected symbol: something

Where 'something' was the thing in double quotes in the class notes.

I found several similar posts to do with escaping backslashes etc. but nothing that handles double quotes.

I tried to strip double quotes from the notes using various combinations of %REPLACE($notes,"\"","")% along the lines of C++ etc but none of them work.

Basically the problem seems to be:

1. Macros (e.g. replace) dont understand %qt%. Thus, %REPLACE($somevar,"%qt%","XXX")% fails, as does %REPLACE($somevar,%qt%,"XXX")%

2. Backslash escapes dont work for \".  Why would the program work for \t and \n but not for everything else which is a special character?

I hope there is a solution for this, other than "Dont use quotes in notes". This needs to be robust.

tia
--Andrew

Pages: [1]