Unless I've missed something obvious, which is entirely possible, adding a --syntax-check-only switch was very easy. I've submitted a pull request with the change: https://github.com/ccrma/chuck/pull/126
I'm going ahead to work on my vscode extension assuming this will (eventually) be there. I doubt I will have it done any time soon because I have no clue what I'm doing, but one day vscode will be able to highlight ChucK syntax errors. On Tue, Jun 11, 2019 at 1:24 AM Jack Atherton <l...@ccrma.stanford.edu> wrote: > I'm not sure if it has one, but it would be pretty straightforward to add > one -- just delete the code generated from the compilation process instead > of sporking it. See chuck_main.cpp: > https://github.com/ccrma/chuck/blob/master/src/host/chuck_main.cpp > > On Mon, Jun 10, 2019 at 7:24 PM Forrest Cahoon <forrest.cah...@gmail.com> > wrote: > >> I'm looking at trying to add more to my ChucK vscode extension, and I'd >> love to be able to run chuck on the code being edited so that I can parse >> and highlight the errors. >> >> However, I don't know how you would run chuck to just generate syntax >> errors. I see there is a --silent switch, which would work for the purpose, >> but would be an unnecessary waste of resources just to get the possible >> syntax errors. >> >> Csound has a --syntax-check-only command-line option. Is there something >> like this for ChucK? If not, would it be straightforward to add one? >> >> Forrest >> >> _______________________________________________ >> chuck-users mailing list >> chuck-users@lists.cs.princeton.edu >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >> > _______________________________________________ > chuck-users mailing list > chuck-users@lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
