New language template - only one output file?

[danm]

Hi,
  I'm generating code for an unsupported language, which has two files (like .h .C). I copies over all the C++ templates to get started, and it's creating C++ files - or I should say file. Only the header.

  I can't find anything in the documentation or help - any idea why it's not generating a body file? Kind thanks for any help.

[Eve]

What you need is an MDG technology that includes Code Options. See http://www.sparxsystems.com/EAUserGuide/index.html?addingcodemodulesinmdgtec.htm

[danm]

Fantastic! Thanks Simon. This is such a great product.

One question, if I'm using a MDG defined language in a project - then I modify the default language templates, then create a NEW MDG file of the same language - what do I get out?

I tried this and the templates got messed up, but maybe I did something incorrectly.

[Eve]

Sorry, I'm not exactly sure what you've done.  Could you detail your steps for me?

[danm]

No Problem

- I create a new project
- In there I create a new language
- In there I edit the code gen templates for that language
- In there I create a new MDG technology file, containing and for that language

Now I create a new project
- I Import and use the MDG tech file just created
- I edit the same code templates (of the language I just created)
- Now, create a second, newer MDG tech file, just like before of the same templates

Does that make sense? I created the MDG tech file to get proper generation of my impl files, but I still need to develop the code templates. Then I want to wrap it up and create a new MDG again, and keep 'leapfrogging' myself.

[Eve]

It should work that way, although when I have done this in the past I imported the technology into my original model.

More recently I have added my technology to the MDG Technology search path. (By default the MDGTechnologies directory where you installed EA)  This method of deployment (and testing) has the advantage that you get equivalent behaviour to the default templates EA provides.

[danm]

Simon,
  OK, I found the problem I believe. Luckily I have an excellent backup program so I didn't lose all my work after I created a MTS file. I believe what happens is that when you save a new language to an MDG - it only saves the templates that have been changed from the default.

  The problem is that if you are 'baselining' your MDG file by creating it, then working from it, you lose the templates you haven't changed. Here's what I mean.
  1. Make a new language
  2. Create MDG from it
  3. Restart using the MDG
  4. Make some further changes
  5. Generate a new MDG
  6. Use the new MDG - oops -  only the last changes are saved, not the originals!

  Your use model makes sense to only save deltas - but it can trip people up. The use model makes sense for modifying supported languages, but for added languages you need to be careful and modify all the templates to resave them.  Maybe just a documentation fix for this one?

  Also - my code datatypes aren't getting preserved in the MDG file for new languages.

[danm]

"Also - my code datatypes aren't getting preserved in the MDG file for new languages."

WRONG! My stupidity - they are being saved of course. What confused me was that I wasn't seeing them in the 'define datatypes' dialog for my language.