Agreed, I don't know if there is a specific ChucK style. LiCK is mostly Java style, many small classes, class extension where appropriate, functor classes where function pointers might have been useful, mixedCaseMethodNames, etc.
https://github.com/heuermh/lick <https://github.com/heuermh/lick> I've written up several issues requesting Java-ish language features to ChucK, but they've sat for a while https://github.com/ccrma/chuck/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+heuermh <https://github.com/ccrma/chuck/issues?utf8=%E2%9C%93&q=is:issue+is:open+heuermh> ChucK kind of is what it is. michael > On Apr 1, 2019, at 11:41 AM, Perry Cook <p...@cs.princeton.edu> wrote: > > Perhaps the Chuck Book might at least provide good examples. > > I don’t know of a formal style guide. I think we authors, while differing > from each other, generally use OOP conventions we brought from C++, Java, > (and myself) Objective C and Smalltalk. > > Prc > > Sent from my iPhone > >> On Apr 1, 2019, at 9:00 AM, chuck-users-requ...@lists.cs.princeton.edu wrote: >> >> Send chuck-users mailing list submissions to >> chuck-users@lists.cs.princeton.edu >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >> or, via email, send a message with subject or body 'help' to >> chuck-users-requ...@lists.cs.princeton.edu >> >> You can reach the person managing the list at >> chuck-users-ow...@lists.cs.princeton.edu >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of chuck-users digest..." >> >> >> Today's Topics: >> >> 1. style manual for coding? (Possibly off topic) (Charlie) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sun, 31 Mar 2019 18:53:29 -0400 >> From: Charlie <taos.poi...@gmail.com> >> To: chuck-users@lists.cs.princeton.edu >> Subject: [chuck-users] style manual for coding? (Possibly off topic) >> Message-ID: >> <CAJVWGib11=e-wf1p-6hrp-uk4mdhrdgeyg-wrgwddvbwhql...@mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" >> >> hey all, >> >> sorry if this is off topic but I'm starting to realize that my haphazard >> coding style is becoming a problem, as I build a live coding practice based >> in ChucK. I'm wondering if there is a "Strunk and White" for coding >> covering stuff like indentation, naming conventions, when to use a function >> or class for something, etc etc. My formal training in coding is limited to >> a FORTRAN class that I took in the 1980s at the Department of Agriculture >> but I've done some stuff in C, so a book oriented around C or C++ would >> probably work. Thanks in advance! >> >> Charlie >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> <http://lists.cs.princeton.edu/pipermail/chuck-users/attachments/20190331/3e9e28d3/attachment-0001.html> >> >> ------------------------------ >> >> _______________________________________________ >> chuck-users mailing list >> chuck-users@lists.cs.princeton.edu >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >> >> >> End of chuck-users Digest, Vol 164, Issue 1 >> ******************************************* > > _______________________________________________ > 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
