Frage zum Treiberimport

IMO....

Yes the order would probably affect position of driver code BUT the drivers should be independent and a change in order should not of itself cause a program to not work. Nor does it play a role in the define block afaik. There you can define things in any order - they are effectively like global variables.

Do you feel there is a situation where this has had an effect?

Interesting.

I was going to say (but thought it might be going off topic) that drivers also have uses clauses, and the order of uses clauses can be important. The reason for that is to do with names of globals (variables, functions or procedures). When you access these in code you write something like



When you look at the assembler it uses a qualified name, something like MyUnit.Mystuff.

The problem is that MyStuff might be defined in multiple units, and just like Delphi, scoping rules (and hence order of placing within uses clauses) apply. Unlike Delphi, though, global variables are more common in AVRCo, so you are more likely to hit this problem, but you definitely can hit the problem with Delphi too. (In fact some hacks in Delphi take advantage of it!)

But this is an issue with uses clauses rather than drivers per se.

So I don't know changing the order of drivers in the import section might have an effect, but I would start with changing the order within the uses clauses first.

But I emphasise - this is just an opinion, not certain knowledge.