Klaus> Hmm, IMHO a somehow "contructed" argument and disadvantage.
Nonsense.
Dito!
Klaus> "`next-window' is a built-in function
Klaus> (next-window &optional WINDOW MINIBUF WHICH-FRAMES WHICH-DEVICES)
Klaus> Documentation:
Klaus> Return the next window after WINDOW in the canonical ordering of
Klaus> windows. If omitted, WINDOW defaults to the selected window. ..."
Klaus> You see the word "canonical"??!!
Yes, I do. You see that word somewhere in the documentation or name
for
`window-list'?
No, unfortunatelly not ;-)
Klaus> If i understand you right then you say it is best to make no
Klaus> specification for API-functions on which programmers can rely
Klaus> because maybe someone wants to change it later and then all
Klaus> already existing code fails or has to be rewritten, right?
No, you didn't understand me right. I didn't say anything of
the sort.
`window-list' already has a specification, and there's no good
reason to
change it, because there's no existing code that assumes a different
specification from it.
This argumentaion now is pure nonsense
If you want a function with a different behavior,
by all means write it and give it a name indicative of what it does.
Ok, i'm not keen wasting valuable time....forget it, i will write my own
(maybe - not probably i must admit - 123534 other people have to do it too ;-)