Hi Steve,

1. The scope of variables is more or less standard Java/C-like -- variables can be used anywhere in the scope in which they are declared or scopes enclosed within, and the underlying values can be passed around to other scopes. File-scope variables can be accessed in pretty much any shred created in that file. Sharing variables across files tends to be more complicated -- the basic paradigm is to make a public class and access static variables or methods within that. 

2. Michael Heuer's LicK is one example of this: https://github.com/heuermh/lick

3. Depending on what your C++ code is doing, you could use a chugin (ChucK plugin). These are generally most appropriate for unit generators and relatively simple generic library functionality. One simple example, Bitcrusher:

https://github.com/ccrma/chugins/tree/master/Bitcrusher

4. The installer should also have installed the command line executable -- you can check this by opening up a window in Terminal and entering a chuck command: 

$ chuck --version

chuck version: 1.3.2.0 (chimera)

   mac os x : intel : 64-bit

   http://chuck.cs.princeton.edu/

   http://chuck.stanford.edu/

$ chuck --help

...

$ chuck path/to/file.ck

etc.

spencer

On Fri, Oct 25, 2013 at 4:20 PM, Steve Morris <steve@judgement.com> wrote:

I'm new to ChucK but am very excited. I have grand plans. I will likely have lots of questions (some unfortunately stupid, apologies in advance) although I have been pouring through manuals, examples, the wiki, git source code and forum archives. Hopefully my questions won't be too annoying. I'm always happy to receive answers in the form of pointers to documentation I should be reading before wasting the groups time. Here's my first pass.

1) I can't find any thing that documents the scope of variables and objects. Can I create variables that can be accessed in other files, other threads.

2) My first project will be fairly large hopefully split between many files. Where can I look to see how ChucK code should be broken down and organized. What is a good paradigm for a shared library.

3) Speaking of libraries I would like to bring a lot of existing C++ code into my project. Does dynamic linking actually work. I see vague (old) references to it being made to work again as if it was broken and other references to it just needing documentation which will come "soon." Lacking documentation is there an example library that does it. I can get a long ways with a working example. Working code may be confusing and slow to understand but it is its own most accurate documentation. I've looked at chuck_dll and I think I need to see the interface from the other side to really understand. I'm happy to be a reviewer for "preliminary" draft documentation.

4) The Mac install seems to have installed a single bundled app. How do I use the command line interface?

Thanks,

-steve (aka zencuke)

_______________________________________________
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