Re: [chuck-users] getting started questions

28 Oct 2013

      Michael,

import.ck is where I saw Machine.Add() used to import. The structure of
LicK showed me the current paradigm for organizing a large code base in
ChucK. Thanks.

Namespaces would be great. They should be nested of course. I wouldn't
think they would be too difficult to add. The basic framework for
namespaces (at least for variable names) clearly already exists. The proof
of that is that different files already have different namespaces. Some
level of import functionality exists as well as a side effect of
MachineAdd() as import.ck demonstrates. It sounds like it is just a matter
of factoring those code fragments out of the Add() method and generalizing
them a little.

Personally I have no objection to using Machine.Add() as the standard
import methodology now that I know it is there. It is sort of strange
making the functionality part of the VM. It would be more natural to make
import a language feature but as long as the functionality exists that's
the important part. I imagine that language enhancements add a whole
different level of development and test complexity.

-steve

On Mon, Oct 28, 2013 at 11:16 AM, Michael Heuer  wrote:
...
Hello Steve, welcome to ChucK!
LiCK is implemented with one public ChucK class (and zero or more
non-public classes) per .ck file and a bunch of Machine.add()
statements in one .ck file (import.ck).  It ain't pretty but it works.
One of my top outstanding ChucK language feature requests is to add
namespaces and import statements so that library/shared code can be
made modular.
I thought I saw somewhere hidden in new features (probably related to
Chugins) that there is a magick library directory where one can place
.ck files and have them loaded at startup.  Might this be a workaround
for having to use the import.ck file explicitly?
michael
...
Another question. I finally found the scope documentation in the shred
...
(obviously not my first guess or this thread wouldn't exist) where I also
found machine.add() which together start to fill major holes in my
understanding. From Lick documentation I deduce that machine.add() does
more
than simply create a shred. It is also a way of including various
declarations and making them available to other shreds. (Note: That is
such
fundamental functionality that it is probably worth stating explicitly
someplace in the ChucK documentation even if it is "just" a side effect
of
sporking.)
However:
inter-shred communication
Shreds sporked in the same file can share the same global variables. They
can use time and events to synchronize to each other. (see events) Shreds
sporked from different files can share data (including events). For now,
this is done through a public class with static data (see classes).
Static
data is not completely implemented! We will fix this very soon!"
This sounds ominous. Should I worry about what part of static data is not
implemented? Are there restrictions to static data I should be wary of.
On Mon, Oct 28, 2013 at 3:24 AM, Steve Morris 
wrote:
...
Thank you Spencer. That's very helpful. I haven't looked at Bitcrusher
yet
...
but besides being chuck full ;-) of useful toys Lick is also a goldmine
of
interesting programming examples. I really learn best by reading code.
Lick
should keep me busy for a while.
-steve
aka zencuke
On Sun, Oct 27, 2013 at 10:47 PM, Spencer Salazar
 wrote:
...
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 
wrote:
...
I'm new to ChucK but am very excited. I have grand plans. I will
...
...
...
...
have lots of questions (some unfortunately stupid, apologies in
advance)
although I have been pouring through manuals, examples, the wiki, git
...
...
...
...
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
On Mon, Oct 28, 2013 at 3:03 AM, Steve Morris 
wrote:
page
likely
source
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
_______________________________________________
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