Angus Leeming wrote:
> You could reasonably define a LyXTabular::npos, no?
I did it to be on the safe side. Now the changes are purely mechanical.
> -int LyXTabular::TeXTopHLine(ostream & os, int row) const
> +int LyXTabular::TeXTopHLine(ostream & os, mynewrowtype row) const
> {
> - BOOST_ASSERT(row >= 0);
> + // FIXME: assert or return 0 as in TeXBottomHLine()?
> BOOST_ASSERT(row < rows_);
>
> I suspect a fudge. Does row < 0 mean something 'special'?
I don't think so, but I am not sure.
A final patch follows after the coord merge, I don't want to create mroe
work for Alfredo.
Georg
