Should a function accept/return values in (row,col) or (col,row) order?
The convention is to address (column, row) like (x, y).
Column refers to the type of value and row indicates the value for the column.
Column is a key and with Row you have the value.
But using (row, column) is fine too.
It depends of what you're doing.
In SQL/Linq, you always refers to Columns to get rows.
Say I have a function that accepts a row and a column as parameters, or returns a tuple of a row and a column as its return value. I know it doesn't actually make a difference, but is there a convention as to whether put the row first or the column first? Coming from math, if I think of the pair as coordinates into the table, I would intuitively put the column first, as in a cartesian point (x,y). But if I think of it as a whole matrix, I would put row first, as in MxN size of a matrix.
If there are different conventions for different languages, I would be interested especially in c++, c# and python.
By "convention" I mean preferably that that language's standard library does it a certain way, and if not that then second choice would be only if it were so universal that all major third-party libraries for that language would do it that way,preferably with an explanation why.