Hi!

-------- Original-Nachricht --------
> Datum: Tue, 3 Jun 2008 17:48:55 +0200
> Von: "Linus Tolke" <[EMAIL PROTECTED]>
> An: [email protected]
> Betreff: Re: [argouml-dev] C++ module preprocessor

> Hello Andreas!
> 
> It is great that you are working with this...
> 
> Are you considering having options to choose from on how to do the import?

We should have at least a list of include paths in the dialog.

Then, Jan pointed out a problem: when you import some system header,
because you need some specific class of method from there, it's very likely,
that this header file will include other header files. So you need some simple
class to display something and end up with dozens (or more) classes, cause
many standard libs depend on each other. We have to find a way to limit at least
the classes in the current diagram, or it'll likely be unusable, since it 
contains
half of the Unix c++ libs or so. we have to check, what info the preprocessor 
adds
when it includes a file. Maybe we could add some info on the directory and only
model classes in or under the current users directory, or so...

> Then we could add options as new ways are implemented. I can think of the
> following alternatives from your example and explanation below:
> O Import plain C++ (source and header files).
>     [ ] Reorder imports, offer to add header file to imports.
>     [ ] Use existing model elements as types and features in the import.

We'd have to pass those types to the parser then. Don't know yet, if it's enough
to just add those types to the qualified_types list. Maybe Luis has better ideas
on this...

> O Preprocess using ArgoUML-builtin preprocessor.
> O Preprocess using Makefile %.E target.

We'd need a Makefile parser then. I'm not aware of one, yet...

But I think, we should start as simple as possible. I just would like to see 
Argo
import Jan's project for now.

Ciao,
Andreas

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to