John and all, hello.
On 22 May 2016, at 1:59, John Cowan wrote:
It's also worth noting that use (or
require-extension, which is the same thing) depends on the module
having
the same name as the file.
Thanks: It did look as if that assumption was baked in somewhere; if the
process
Evan and all, hello.
On 22 May 2016, at 3:15, Evan Hanson wrote:
A quick note about units and modules: the two are different things
used
for different purposes. The former has to do with controlling the
compilation and linking of separate application components, whereas
the
latter is about
Hi Norman,
A quick note about units and modules: the two are different things used
for different purposes. The former has to do with controlling the
compilation and linking of separate application components, whereas the
latter is about namespace management. The hunt continues for the best
way to
Norman Gray scripsit:
> A puzzle: in his message John mentioned that 'Use [...] installs the
> file and imports it into the current module.' I'm puzzled at this
> use of 'install'.
It should have been "loads". It's also worth noting that use (or
require-extension, which is the same thing)
Greetings.
On 16 Mar 2016, at 17:01, Norman Gray wrote:
Thank you Oleg and John, for these explanations. I won't be back in
Chicken-land for a couple of days, but as soon as I can I'll aim to
understand this point well enough to offer a draft of additional text
for the manual.
A little
Norman Gray scripsit:
> First: what (I think) I understand about compilation units.
Units go back to Chicken 3. IMAO, you don't need to know anything
about them unless you are writing code to be incorporated into
the main Chicken build, which is unlikely.
> * import libraries
An import
Greetings.
...again, on my second day with Chicken. I can't easily tell from the
docs what is the idiomatic pattern for usage of Chicken modules. Can
anyone point me to a reference?
[ I hope it's useful to ask these somewhat beginner questions. When I
become less naive about Chicken I
