Reverse selector ordering... why?

[Frifox]

To make things simple, lets assume my master xcss to be:
------------------------
#wrapper {
self {
...
}
.header {
...
}
.footer {
...
}
}

All is good and I expect the end result to be:
------------------------
#wrapper {
...
}
#wrapper .header {
...
}
#wrapper .footer {
...
}

but instead i get
------------------------
#wrapper .footer {
...
}
#wrapper .header {
...
}
#wrapper {
...
}

I'm developing a site with total CSS line count being 1.5k+ lines, and
in some cases the order DOES matter. Is there any specific reason why
xCSS prints the parsed CSS backwards?

[Anton Pawlik]

if you need to push something to the top you just need to add a (,) to the selector. ive explande the reason many times please search the forum.

[Andrew]

I've search the forum for "order", "ordering", "selectors" and "select" and didn't find the reason. Can you point me to the post that answers their question?

Thanks