Thanks. And like, that sounds a lot more sensible than what I'm trying to
do :)
And what I'm trying to do doesn't strike me as generally a good idea, but...
Initially I was playing around with language-stuff. Was making a language
and wanted a file written in that language to define a signature a
This doesn't quite answer your question, but another possibility that would
allow you to separate the a@ and b@ unit implementations in separate files
is to put all of your signature definitions in a single file that will be
required by both "a.rkt" and "b.rkt". In my experience, this strategy is
f
Hello people,
I've been fumbling around with cyclic dependencies and such and have started
looking at signatures and units. I manage to make the cycles work out in a
couple different ways, but I'm running into trouble when I try to put different
parts in different files the way I want them. As
3 matches
Mail list logo
