export/re-export

[Martin Grabmueller]

Hello list,

with --disable-deprecated, the current CVS Guile complains about the
use of `export' in (srfi srfi-13).  Since I don't know how to handle
this, I'd like to know what others think.  The the output of

  GUILE_WARN_DEPRECATED=detailed make check

is as follows:

  Testing libguile/guile ...
  with GUILE_LOAD_PATH=.:./test-suite
  with LTDL_LIBRARY_PATH=/home/mgrabmue/cvs/guile/guile-core/srfi/.libs:
  Using `export' to re-export imported bindings is deprecated.  Use `re-export' 
instead.
  (You just re-exported `string->list' from `(srfi srfi-13)'.)
  (You just re-exported `string-copy' from `(srfi srfi-13)'.)
  (You just re-exported `string-fill!' from `(srfi srfi-13)'.)
  (You just re-exported `string-index' from `(srfi srfi-13)'.)
  (You just re-exported `string-upcase' from `(srfi srfi-13)'.)
  (You just re-exported `string-upcase!' from `(srfi srfi-13)'.)
  (You just re-exported `string-downcase' from `(srfi srfi-13)'.)
  (You just re-exported `string-downcase!' from `(srfi srfi-13)'.)

  Totals for this test run:
  passes:                 1882
  failures:               0
  unexpected passes:      0
  expected failures:      17
  unresolved test cases:  0
  untested test cases:    0
  unsupported test cases: 9
  errors:                 0

  PASS: check-guile
  ==================
  All 1 tests passed
  ==================

The problem with this is that these variables are not re-exported from
the core definitions, but are exports of the procedures defined in
srfi-13.c.  Is there any possibility to handle this cleanly, i.e. to
override builtin procedures without causing such warnings?

Thanks,
  'martin