This also sounds similar to some of the issues I dealt with in some
experimental code I wrote to simulate the result of precompiling modules.
In `eval_expr`, I dealt with the ability to handle some expressions
specially (such as `=`) and to recurse into `module` declarations. (The net
goal of t
Cool, thank you.
On Mon, Sep 26, 2016 at 9:09 AM, Yichao Yu wrote:
> On Mon, Sep 26, 2016 at 8:31 AM, Cedric St-Jean
> wrote:
> > It would make sense to put .jl file-parsing code in a separate,
> > community-maintained module, because the rules for finding which file a
> > module corresponds to
On Mon, Sep 26, 2016 at 8:31 AM, Cedric St-Jean wrote:
> It would make sense to put .jl file-parsing code in a separate,
> community-maintained module, because the rules for finding which file a
> module corresponds to are not trivial, and can change over time (they became
> case-sensitive in 0.5)
It would make sense to put .jl file-parsing code in a separate,
community-maintained module, because the rules for finding which file a
module corresponds to are not trivial, and can change over time (they
became case-sensitive in 0.5)
It's too bad that
macro module_parser(m)
m
end
@module_p
Hello colleague,
On Monday, September 26, 2016 at 12:50:44 AM UTC+2, Cedric St-Jean wrote:
>
> I faced very similar issues with ClobberingReload.jl.
> https://github.com/cstjean/ClobberingReload.jl/blob/master/src/ClobberingReload.jl
> Check
> out parse_file (courtesy of @stevengj), parse_modul
I faced very similar issues with ClobberingReload.jl.
https://github.com/cstjean/ClobberingReload.jl/blob/master/src/ClobberingReload.jl
Check
out parse_file (courtesy of @stevengj), parse_module, and creload. I
haven't "expanded" the includes, but it seems straight-forward to do with a
compre