Splitting of ASM source files

Thanks for your help!
I tried it with include directives (thought it works like a preprocessor).
Now I read something about PUBLIC and EXTRN, like you suggested. But the effort of making all my variables public and defining them as extrn is really big. So I decided not to split the files.
Thanks for your help anyway!

Have a nice day!
Reinhard

Thanks for your help!
I tried it with include directives (thought it works like a preprocessor).
Now I read something about PUBLIC and EXTRN, like you suggested. But the effort of making all my variables public and defining them as extrn is really big. So I decided not to split the files.
Thanks for your help anyway!

Have a nice day!
Reinhard

"But the effort of making all my variables public and defining them as extrn is really big."

You don't need to make them all Public - only the ones which actually need to be accessed between files.

Like I said before, Your modules will have to be properly structured - that's a design issue; not something you can just hack in as an afterthought! ;-)
The object is to have the minimum "coupling" between "modules"

Yes, I know....
but now it's to late to structure the files *gg*
i keep some kind of overview by setting bookmarks.

"it's to late to structure the files"

maybe you need to just put this one down to experience, and think about getting it right from the start with your next project?

"i keep some kind of overview by setting bookmarks."

On the other hand, it sounds like you are setting yourself (and/or your successors) a maintenance nightmare - so maybe you owe it to yourself (and/or your successors) to sort the mess out now!

Then again, this is the sort of thing that keeps the likes of me in business - so you just hang in there with your spaghetti maker!! ;-)

On the other hand, it sounds like you are setting yourself (and/or your successors) a maintenance nightmare - so maybe you owe it to yourself (and/or your successors) to sort the mess out now!

This is where you need to realize that creating well structured programs is a selfish thing. Even when you are sure you will never see it again it WILL come back to haunt you. In my early days, I stupidly did a couple of "since this will never change, who cares" designs and lived to regeret it. Also, I have, on numerous occasions, refused to change programs unless I were given time to structure them first.

Erik

"Even when you are sure you will never see it again it WILL come back to haunt you."

Beware the Proven Product!! :-0