Imagine that last email had a nice descriptive subject, like this one.
Evan
Thanks megane!
On 2021-04-22 14:00, megane wrote:
> ITYM it'll never trigger an error, even if the the filname is symbol for
> example.
In the use case where FILENAME is a string you will hit this:
$ csc -analyze-only - < to be added to the alist of
import libraries, leading to an error
Evan Hanson writes:
Thanks, pushed.
> This is intended to check for a pair of strings when this declaration is
> used in its `(MODULENAME FILENAME)' form, but we currently use `string'
> instead of `string?' to check the second item, which will always trigger
> an error ("bad argument type").
Evan Hanson writes:
> Cool, here is a signed off copy. But, I made some small changes, so if you
> or another hacker could have a look just to make sure you're OK with
> it?
Looks good, pushed!
>
> I fixed two places where the `resolve-variable` procedure didn't have the new
> `outer-ln`
