guile-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

guile-1.5.1 and deprecated ...


From: David Pirotte
Subject: guile-1.5.1 and deprecated ...
Date: Wed, 22 Aug 2001 15:25:35 +0200

;; 1.

i have absolutely no idea what scheme and/or guile function lead
to the following deprecated message:

        `scm_make_gsubr' is deprecated.  Use `scm_c_define_gsubr' instead.
        `scm_sysintern' is deprecated. Use `scm_define' instead.
        `scm_register_module_xxx' is deprecated.  Use extensions instead.

;; 2.

i also don't know what the following means: 

        Autoloading of compiled code modules is deprecated.
        Write a Scheme file instead that uses `load-extension'.
        (You just autoloaded module (struct gtrees).)           <==

i use 

        (define-module (... ...)
          :use-module ...
          )

        everywhere in my code, but i don't see what the problem is

and yes, different modules (my modules) use (struct gtrees)     <==

;; 3.

        Using `export' to re-export imported bindings is deprecated.  Use 
`re-export' instead.
        (You just re-exported `id' from `(alto db-utils db-attr-def)'.)
        (You just re-exported `show-me' from `(alto db-utils db-tb-def)'.)
        (You just re-exported `show-me' from `(alto db-utils db-tb-cl-mt)'.)
        (You just re-exported `show-me' from `(alto db-utils db-con)'.)

this sounds crazy: almost all of my modules use goops, define classes, and i
almost systematically define a show-me method (not to say that almost all 
classes
i define do have a 'id or 'ref accessor, exported of course

so, if i don't know the order in which these modules will later be 'used' by new
modules, how can i know where to use export and where to use re-export? or 
should
i use re-export everywhere !?!



reply via email to

[Prev in Thread] Current Thread [Next in Thread]