scm_out_of_range_pos()

[Martin Baulig]

Hi,

is there any reason why there's both scm_out_of_range() and
scm_out_of_range_pos() instead of checking whether pos != 0 like
in scm_wrong_type_arg() ?

The behavior of the VALIDATE macros is currently inconsistent if
you pass pos == 0 - most of them (which are using SCM_ASSERT) print
the correct error message - and the ones which are using SCM_ASSERT_RANGE
print "... argument 0 ..." in the error message.

-- 
Martin Baulig
address@hidden (private)
address@hidden (work)