Further Notes On Extends about less-docs

[seven-phases-max]

Don't understand: Notice that the Extending selector was grouped before the Extended selector. ...

I guess this means something like:

.questions:extend(.answers) {
    background: blue;
}

.answers {
    color: red;
}

with result:

.questions {
  background: blue;
}
.answers,
.questions {
  color: red;
}

I.e. .answers goes first in the list even if defined after .questions. (Probably it's too minor stuff to be mentioned at all)

[lukeapage]

Except its reverse.. the extending selector goes last in the list? (I guess depending on the definition of extending selector). Also the xamples that were around this were the wrong way round too. I think I worked it into some of the sentences anyway that it is added on to the end of the selector list.

[jonschlinkert]

I did all of the initial docs for extends while we were still discussing how you were going to implement it, so I imagine a lot of it was wrong

[seven-phases-max]

Actually those "extending" and "extended" labels are not so easy to define unambiguously. Hence sometimes we can even confuse ourselves.
For example a:extend(b) looks like a extends b. So we may say that

a is the "extending" and b is the "extended".

However, since it's a who inherites b's properties, it is also true that

a is extended by b's properties

so it's

a is extended by b

so it's

a is the "extended" and b is the "extending"

:)

It all depends on how exactly one defines "extend" (as English word not as LESS keyword) in context of CSS classes... and the flip point is very thin and subtle... (Luckily examples make things unambiguous).

[lukeapage]

Cool Jon, thanks, makes sense now & feel free to critique or add to the
extend documentation