\f
-;;; {#/app}
+;;; {The (app) module}
;;;
;;; The root of conventionally named objects not directly in the top level.
;;;
-;;; #/app/modules
-;;; #/app/modules/guile
+;;; (app modules)
+;;; (app modules guile)
;;;
;;; The directory of all modules and the standard root module.
;;;
;; To make your Guile extension into a dynamic linkable module, follow
;; these easy steps:
;;
-;; - Find a name for your module, like #/ice-9/gtcltk
+;; - Find a name for your module, like (ice-9 gtcltk)
;; - Write a function with a name like
;;
;; scm_init_ice_9_gtcltk_module
;;
;; and put it somewhere in %load-path.
;;
-;; - Then you can simply write `:use-module #/ice-9/gtcltk' and it
+;; - Then you can simply write `:use-module (ice-9 gtcltk)' and it
;; will be linked automatically.
;;
;; This is all very experimental.
;;;;
\f
-(define-module #/ice-9/debug)
+(define-module (ice-9 debug))
\f
;;;;
\f
-(define-module #/ice-9/hcons)
+(define-module (ice-9 hcons))
\f
;;; {Eq? hash-consing}
\f
-(define-module #/ice-9/lineio)
+(define-module (ice-9 lineio))
\f
;;; {Line Buffering Input Ports}
\f
-(define-module #/ice-9/mapping
- :use-module #/ice-9/poe)
+(define-module (ice-9 mapping)
+ :use-module (ice-9 poe))
(define-public mapping-hooks-type (make-record-type 'mapping-hooks '(get-handle
create-handle
;;;;
\f
-(define-module #/ice-9/poe
- :use-module #/ice-9/hcons)
+(define-module (ice-9 poe)
+ :use-module (ice-9 hcons))
\f
;;; installed-scm-file
-(define-module #/ice-9/slib)
+(define-module (ice-9 slib))
\f
\f
-(define-module #/ice-9/tags)
+(define-module (ice-9 tags))
;;;;
\f
-(define-module #/ice-9/threads)
+(define-module (ice-9 threads))
\f