Move includes from Package.h into Package.c to minimize debugging information

[Adrian Pop]

At least on Windows the omc executable has 300-400Mb which is huge
and makes debugging very slow. I suspect this happens because we
include a lot of .h files everywhere.

Currently all the includes are in Package.h and they should be moved into Package.c

Maybe even split Package.h into Package.public.h and Package.private.h and only include the Package.public.h into other .c files and the Package.private.h into Package.c.

[Mahder Alemseged Gebremedhin]

Partially fixed in r22149 by moving all the includes from the header files to the source files.

Maybe even split Package.h into Package.public.h and Package.private.h

This will also help a lot. Specially for files like ExpressionSimplify.mo. It has 19 public functions and 99 protected functions.

We can also declare only the public functions in Package.h file and put all protected function declarations in the Package.c file (or maybe even not declare them at all and suppress the warnings.)

I think splitting is much cleaner though.

[Martin Sjölund]

You can't remove them because C99 requires function prototypes to be present. Also, even if we suppress warnings, you get wrong results because the implicit arguments will typically use type int and we use long. Etc.

I would move protected declarations into the C file and also make them static functions (so other files cannot link against them).

[Martin Sjölund]

DAE.FUNCTION now has a field SCode.Variability variability. I did not do anything with it yet.

[Martin Sjölund]

The SimCode now moves protected functions out of the header into the C-file. They are also declared static instead of with external linkage.

[Martin Sjölund]

Has this been fixed yet?

[Adrian Pop]

I think so, yes.

[Martin Sjölund]

Milestone renamed

[Martin Sjölund]

Milestone renamed