Scope and the order of declarations/definitions.

[seven-phases-max]

(I linked to the "Scope" section from 1868, read it and...)
It states:

Note that the order of declaration does matter.

This is misleading. The order of declarations does not matter actually . E.g. the following two examples are equal:
(A):

@var: red;

#page {
  @var: white;
  #header {
    color: @var; // white
  }
}

(B):

@var: red;

#page {
  #header {
    color: @var; // white
  }
  @var: white;
}

---

Not counting a few language dark corner cases and issues similar to those mentioned in 1399 where the order of definition is indeed important (usually just involving some recursive (re)definitions and cycling dependencies)).

---

I decided to create this ticket first just in case someone has any/other ideas for improving/rewording this docs section.

[seven-phases-max]

Also not counting that in case of "re-definition" the last declaration wins (so in that context the order would matter), but this is somewhat beyond the scope of the "Scope" section.

[matthew-dean]

It does matter. What this means is that it matters within a scope.

[seven-phases-max]

Aha, so I was a bit hurrying t close this.

What this means is that it matters within a scope.

That makes sense. Though the way it was originally written (stressed does right before the example) it really was confusing (making an illusion that the colour is white because of the variable definition order and not because of the scope visibility).

Assuming that section is just an introductory section of the language overview (so we don't probably want to bring all those "last declaration wins" details there with tons of ifs and whens, e.g. "for the scopes themselves the order does not matter" vs. "within a single scope the standard 'last definition of the variable is used' rule applies") - How about changing current:

Note that the order of declarations does not matter so the following Less code is identical to the previous example...

to something more neutral like:

Variables and mixins do not have to be declared before being used so the following Less code is identical to the previous example...

?

(I.e. not mentioning any "order" stuff at all since this is described later in "Lazy Loading" linked with "See also")

[lukeapage]

Sounds better to me

[seven-phases-max]

Closing as fixed in the docs.