Appendix E. File I/O
Like all software, ChucK programs often need a way to save data for when they stop running and to reload that data when they resume running. They also need a way to read data generated by other programs or written manually by a human and to output data that can be used by another program or examined by a human. If you think this sounds like a good use for files, then you’re correct. Files are the backbone of any complex software ecosystem, and naturally ChucK provides several easy-to-use mechanisms to work with them.
E.1. File basics
The FileIO class is ChucK’s primary mechanism for interacting with files, providing a number of standard mechanisms for file input and output. Each instance of FileIO corresponds to a single ...
Get Programming for Musicians and Digital Artists now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
