I just was thinking: C++, Java, SuperCollider, Python, SmallTalk, processing, etc. all use studlyCaps as the standard for object and method names rather than the GNU C under_score_object_names or the Max/Pd-style runeverythingtogether (natural for German and Thai speakers, but not most languages AFAIK).
Should we make the new Pd libraries use capsAsTheStandardNameFormat? I am beginning to think yes...
.hc
________________________________________________________________________ ____
If you are not part of the solution, you are part of the problem. - Eldridge Cleaver
On Sat Mar 25, 2006 at 09:45:52PM -0500, Hans-Christoph Steiner wrote:
I just was thinking: C++, Java, SuperCollider, Python, SmallTalk, processing, etc. all use studlyCaps as the standard for object and method names rather than the GNU C under_score_object_names or the Max/Pd-style runeverythingtogether (natural for German and Thai speakers, but not most languages AFAIK).
i think its called camelCase in some circles. no idea why, as i can't read Arabic..
pd symbols can have spaces, so do we even need underscores? i find eather solution incongruous and not idiomatic with pd
Should we make the new Pd libraries use capsAsTheStandardNameFormat? I am beginning to think yes...
On Sun, 26 Mar 2006, carmen wrote:
On Sat Mar 25, 2006 at 09:45:52PM -0500, Hans-Christoph Steiner wrote:
I just was thinking: C++, Java, SuperCollider, Python, SmallTalk, processing, etc. all use studlyCaps as the standard for object and method names rather than the GNU C under_score_object_names or the Max/Pd-style runeverythingtogether (natural for German and Thai speakers, but not most languages AFAIK).
i think its called camelCase in some circles. no idea why, as i can't read Arabic..
Ruby uses underscores in methodnames and CamelCase in classnames.
Most LISPs and Schemes use dashes.
Most of the C/POSIX API does alltogetherwordsclumping, often without vowels.
pd symbols can have spaces, so do we even need underscores? i find eather solution incongruous and not idiomatic with pd
If we switch to unicode then we can use *smileys* instead of spaces or underscores. That'll make all Pd users much happier.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
On Mar 26, 2006, at 12:11 AM, Mathieu Bouchard wrote:
On Sun, 26 Mar 2006, carmen wrote:
On Sat Mar 25, 2006 at 09:45:52PM -0500, Hans-Christoph Steiner wrote:
I just was thinking: C++, Java, SuperCollider, Python, SmallTalk, processing, etc. all use studlyCaps as the standard for object and method names rather than the GNU C under_score_object_names or the Max/Pd-style runeverythingtogether (natural for German and Thai speakers, but not most languages AFAIK).
i think its called camelCase in some circles. no idea why, as i can't read Arabic..
Ruby uses underscores in methodnames and CamelCase in classnames.
Most LISPs and Schemes use dashes.
Most of the C/POSIX API does alltogetherwordsclumping, often without vowels.
C/POSIX uses a lot of arbitrary abbreviations and is not something to emulate, in my book.
arbitrary-abbreviation with whole word: fnmatch first 3 consonants: strcmp, strcpy whole word with truncate: opendir, readdir, closedir
.hc
pd symbols can have spaces, so do we even need underscores? i find eather solution incongruous and not idiomatic with pd
If we switch to unicode then we can use *smileys* instead of spaces or underscores. That'll make all Pd users much happier.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
________________________________________________________________________ ____
If you are not part of the solution, you are part of the problem. - Eldridge Cleaver
On Mar 25, 2006, at 11:08 PM, carmen wrote:
On Sat Mar 25, 2006 at 09:45:52PM -0500, Hans-Christoph Steiner wrote:
I just was thinking: C++, Java, SuperCollider, Python, SmallTalk, processing, etc. all use studlyCaps as the standard for object and method names rather than the GNU C under_score_object_names or the Max/Pd-style runeverythingtogether (natural for German and Thai speakers, but not most languages AFAIK).
i think its called camelCase in some circles. no idea why, as i can't read Arabic..
I stand corrected, StUdlyCaPs is a little different than CamelCase.
http://en.wikipedia.org/wiki/CamelCase http://en.wikipedia.org/wiki/StudlyCaps
pd symbols can have spaces, so do we even need underscores? i find eather solution incongruous and not idiomatic with pd
Spaces in object names would cause a lot of pain, I think, since Pd doesn't deal with symbols with spaces very well. Even if it did, I think it would make things unclear as to which words are part of the object name, and which are arguments.
.hc
Should we make the new Pd libraries use capsAsTheStandardNameFormat? I am beginning to think yes...
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
________________________________________________________________________ ____
"I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits." - Martin Luther King, Jr.
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
Should we make the new Pd libraries use capsAsTheStandardNameFormat?
This can be a problem with operating systems not being able to know and uppercase from a lowercase letter.
Ciao
On Mar 26, 2006, at 2:51 AM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
Should we make the new Pd libraries use capsAsTheStandardNameFormat?
This can be a problem with operating systems not being able to know and uppercase from a lowercase letter.
Both NTFS and HFS are case-preserving but not case-sensitive. So while both filesystems will store and display the correct caps, you'd be able to use any kind of caps in object boxes and it would work.
So yes, it would cause problems if people don't write the correct caps, but that's already a problem. For example. pixelTANGO uses an object called [stripPath], but [strippath] exists first in the path. So when using [stripPath], Pd tried to load [strippath] first, but its a C object, and C is case-sensitive, so Pd couldn't find the symbol _stripPath_setup. It then fails, and then opens stripPath.pd.
.hc
________________________________________________________________________ ____
"The arc of history bends towards justice." - Dr. Martin Luther King, Jr.
-
carmen -
Frank Barknecht -
Hans-Christoph Steiner -
Mathieu Bouchard