Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] Module System

I think it'll be tricky but worth it.

Just a note, I revised the proposal in the PR to focus on using
Python-style import syntax rather than Javascript. This is mainly
because JS ties in object destructuring syntax into its import system,
which works well but it isn't something that makes sense with Csound
IMO. Python's import syntax is pretty clear to me and I think it would
fit in nicely with Csound orc language. The one thing would be that
we'd have to use a convention for file names (i.e., files must end in
.orc, similar to how python modules have to be files that end in .py
or .pyc).

On Fri, Oct 31, 2025 at 1:48 PM Victor Lazzarini
<[email protected]> wrote:
>
> Looks good to me, but sounds like hard work.
>
> I think fixing name clashes is a very good idea, in fact something essential really even outside the scope of this module system.
>
> Prof. Victor Lazzarini
> Maynooth University
> Ireland
>
> > On 31 Oct 2025, at 17:06, Steven Yi <[email protected]> wrote:
> >
> > *Warning*
> >
> > This email originated from outside of Maynooth University's Mail System. Do not reply, click links or open attachments unless you recognise the sender and know the content is safe.
> >
> > Hi All,
> >
> > I did some brainstorming in a long session with AI and produced a plan
> > for file-based modules for Csound. I've posted a summary at:
> >
> > https://github.com/csound/csound/issues/2340
> >
> > The idea for backwards compatibility is that #include works as-is but
> > import uses the proposed module-based system, and to encourage users
> > to adopt import over #include moving forward.
> >
> > I think for feedback it might be good to carry on on the github issue
> > rather than on the mailing list here.
> >
> > Thanks!
> > steven