Book a Demo

Author Topic: Relative path to sourcecode  (Read 3348 times)

ceze

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Relative path to sourcecode
« on: July 11, 2006, 09:48:39 am »
It would be nice if one could choose the path to sourcecode to be relative the .eap-file. I for instance work on projects on more than one computer (offline) and has to move the project back and forth.
It would also be great when distributing soure code packages.

When I'm here I just wan't to mention a few things more. Source code generation seems to always mess up the source file, to bad since it is a really really good function otherwise (I code in C++).
What I mean with "mess up":
* Mixing up and switching method bodies with thier definitions (occurs on methods with different qualifiers).
* Moving header comments between methods.
* The parser doesn't always seem to understand inline functions, especially inline template functions outside the class definition.

(sorry if these are already known issues but hey.. they are well appreciated features)

Great UML tool 8) can't wait till the final version!
/Johan

thomaskilian

  • Guest
Re: Relative path to sourcecode
« Reply #1 on: July 12, 2006, 05:45:07 am »
Actually you can use relative paths in EA (and it work in most places). Unfortunately it does not generate relative paths automatically. So I second this: Can we pls. have a switch to generate relative instead of absolute paths?

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Relative path to sourcecode
« Reply #2 on: July 20, 2006, 11:12:56 pm »
Quote
* Mixing up and switching method bodies with thier definitions (occurs on methods with different qualifiers).
* Moving header comments between methods.
* The parser doesn't always seem to understand inline functions, especially inline template functions outside the class definition.

Are you able to provide examples of these?  I haven't seen these problems at all.