include files

rogan · Posted: Sun Dec 16, 2007 4:54 pm Post subject: include files

Hi all,

Is there any way to include files? I know that `machine.add' will chuck files for me (so I can make sure my classes have been loaded), but is there any way that I can include code like in C? I'd like to break my code into "header" and "main" to separate functions from scores, and miniaudicle stuff from unit generators.

Thanks!
Rogan

davebotpdx · Joined: Dec 18, 2007 Posts: 2 Location: portland, or

Rogan,

Maybe you can help me out, I've got a question about something you wrote.

Say I've got a instrument class Sampler.ck.
The following doesn't work for me:

//------somefile.ck-------//

Machine.add("Sampler.ck");

Sampler s;

//---------------------------//

Are you getting this to work? I can get it to work only by first loading
the class from outside of this file. (and removing the .add line)

Thanks very much,
dave

Kassen · Posted: Tue Dec 18, 2007 12:25 pm Post subject:

Welcome &welcome!

The issue is that a file first gets parsed for syntactic correctness, then compiled to the VM and executed.

So, in your "sampler" case the parser discovers that you use a class that hasn't yet be defined and so brings that to your attention (as well as going on strike from there on!), if ChucK would somehow continue beyond this it would find that the class would get defined before it would get used but things don't happen in that order as we have a compile stage before it actually runs.

The solution would indeed be to have a sort of "include" facility that would take effect before parsing the rest, this is being worked on.

For now, what you can do is have a sort of "mother" file that adds all your classes for you, then adds the actual program. This works but it can get inconvenient.

Hope that helps.

davebotpdx · Joined: Dec 18, 2007 Posts: 2 Location: portland, or

That does help. Do you think this compiler behavior will change in the future?

What I have been doing was to have a class loader file, and then separate programs.
But, what your saying is these can be combined to have:

Machine.add ( "the class I want to load" );

Machine.add ("the chuck program I want to run using that class above" );

That should be fine. Thanks for your help.

-dave

rogan · Posted: Tue Dec 18, 2007 3:30 pm Post subject:

Hi all,

Thanks for the replies. The 'mother' file is a good idea. I think I'll start using that. I'm definitely looking forward to normal include files (as I wrote above), for just normal code cleanliness. Maybe if I score some free time soon, I'll take a look at the Chuck code....

Cheers,
Rogan

Kassen · Posted: Wed Dec 19, 2007 10:43 am Post subject:

Frostburn · Posted: Wed Dec 19, 2007 2:17 pm Post subject:

I find the POV-ray way of doing include files quite practical.
typing:

Kassen · Posted: Wed Dec 19, 2007 3:10 pm Post subject:

lamarcph · Posted: Wed Dec 19, 2007 3:35 pm Post subject:

Until there is a "build in" solution I use a little java app I made.
It recursively looks for "!#import filename" tags in comments and add that file to the chuck command line, in reverse order.

The same sort of thing could be done at chuck_main.cpp ln 590. It's easier to that in comments because you don't need to worry about the chuck parser.

What I would really love is a import functionality and a chuck symbolic parser that would provide "auto-complete" of user and standard data type. =!Maybe!= we could modify miniaudicle to do that. That and flat files access, and a xml parser! ok, I am dreaming.

Kassen · Posted: Wed Dec 19, 2007 3:46 pm Post subject:

Didn't Spencer say he wanted auto-complete in the Mini for build-in stuff and user defined things? I'm fairly sure he's going to do that but I haven't seen him 'round for a while.