Re: [chuck-users] Chuck Coding Style (Charlie)

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-request@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-request@lists.cs.princeton.edu

You can reach the person managing the list at chuck-users-owner@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 To: chuck-users@lists.cs.princeton.edu Subject: [chuck-users] style manual for coding? (Possibly off topic) Message-ID: 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