Re: Let's talk about scope
>i'm currently working on a rather large project which has, at the moment,
21
>include files, which have many conflicts. My solutions was to first
include a
>vars.e which had all global variables and types (i figure types with the
same
>name have the same definition...). Then i took out all the includes in
>include files and included them in the main program above their callers.
>After removing all local types and includes in the include files, i had a
>grand total of 1 naming conflict (upper defined in both sfx2.e and
>wildcard.e). The disadvantage: everything is pretty much global. So
what;
>it already is. The advantage: no conflicts. The program runs fine.
You've reordered the entire project, including all include-files.
>something to think about
I did. It looks like a lot of messy work to me. And it reminds me of basic.
Anyone should feel free to say that re-ordering huge projects, and having
special versions of each library, is fun to do. I disagree though.
Ralf
|
Not Categorized, Please Help
|
|
