On Sun, Jul 21, 2019 at 6:21 AM Christopher Lam
wrote
In experiments converting legacy code to use srfi-9 records, I'm finding
> the latter doesn't travel well across modules.
>
In SRFI 9 you need to define a record type in exactly one module and then
export whatever subset of the constructor, p
Hello Arne!
Thanks for posting those links!
I think your "already defined macro check" is part of what I was looking
for. I say part, because I was looking for something, that probably does
not exist: Something that checks for existing macros and for existing
procedures or other after compile-tim
Hi Mark!
On 7/21/19 4:56 AM, Mark H Weaver wrote:
> Hi Zelphir,
>
> Zelphir Kaltstahl writes:
>
>> At first I had the macro use `define`, but then I thought: "What if I
>> want to conditionally define a route procedure?". My guess is, that then
>> the define form would be inside some `cond` or `i
Hi All
In experiments converting legacy code to use srfi-9 records, I'm finding
the latter doesn't travel well across modules.
See simple code below -- m1.scm runs fine however m2.scm borks when
creating srfi-9 record object
Any clue why srfi-9 can't be exported?
For various reasons I must keep
