> The `configure-runtime` submodule name is special: when "main.rkt" is
> run as a program, then `configure-runtime` is loaded and instantiated
> first --- before the result of "main.rkt", and before the imported
> "foo.rkt" and "bar.rkt" modules.
>
> This strategy only makes sense for configuratio
Matthew Flatt writes:
> Every once in a while, I find that option 2 works well with the pattern
>
> foo.rkt:
>#lang racket
>(define-logger foo) ; uses `(current-logger)`
>
> bar.rkt:
>#lang racket
>(define-logger bar) ; uses `(current-logger)`
>
> main.rkt:
>#lang racket
>
Yes, I agree that option 1 sounds better.
Every once in a while, I find that option 2 works well with the pattern
foo.rkt:
#lang racket
(define-logger foo) ; uses `(current-logger)`
bar.rkt:
#lang racket
(define-logger bar) ; uses `(current-logger)`
main.rkt:
#lang racket
(
What's a sane way to set up hierarchical loggers among a set of modules
within a program? Say the main program file main.rkt has a logger named
'main, and it "require"s module foo which has a logger 'foo, whose
parent should be 'main. Module foo also "require"s module bar, which
has its own l
4 matches
Mail list logo
