• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WOPopUpButton
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOPopUpButton


  • Subject: Re: WOPopUpButton
  • From: Timmy <email@hidden>
  • Date: Thu, 21 Jun 2007 22:49:31 -0700

On Jun 21, 2007, at 9:11 PM, Ian Joyner wrote:

On 22/06/2007, at 12:39 PM, Eric Robinson wrote:

On Jun 21, 2007, at 7:29 PM, Ian Joyner wrote:

On 22/06/2007, at 6:43 AM, David LeBer wrote:

On 21-Jun-07, at 2:15 PM, Sigurður E. Vilhelmsson wrote:

I figure I need to build an NSArray and populate it with the values
from the Course_description table and then use that to populate the
course_descriptionID in the Course table, but exactly how to do that
is just out of my reach.

First thing, your naming convention looks a little wonky. Java usually uses CamelCase for class and method names.

Hmm. Thanks David, I hadn't heard the term CamelCase before. Is that because camels are unrideable and CamelCase is unreadable?


http://web.mac.com/joynerian/iWeb/Ian Joyner/Readability.html


This is probably sending this discussion waaay off topic, but whatever.

Right.

Whether you like it or not, infix caps, or camel case, are part of the Official Code Conventions of the Java Programming Language, seen at http://java.sun.com/docs/codeconv/html/CodeConventions.doc8.html#367 . You may personally like underscore method names more than camel case. I personally do as well, but...


Every piece of code you write with non-standard naming conventions results in anyone who "follows the rules" with respect to Java programming to have to mentally switch contexts with regard to method calls, class declarations, etc... Often within the same line of code. You can't get away from camel case even if you tried. WO, WOnder, and the java apis all use it.

In the end, camel case isn't that bad, and it makes you a good citizen. Swallow your pride and getOverIt.

It's the other way around actually. CamelCase is spurned by typographers for good reason. I guess Lemmings must be really good citizens. I'd rather think different, nothing to do with swallowing pride. Pride is arrogantly sticking with something that is wrong.

Two things:

"Pride" would be arrogantly and self-importantly sticking with any position, right OR wrong.

And, arrogance had nothing to do with the reasons Eric enumerated for using CamelCase. As a matter of fact, I doubt any of us use CamelCase out of arrogance. Now, if we were to take the time blog about and compare code "typographies" to written verse, then make sure everyone sees it..... :-)

Nevermind. I think it is probably better said as such:

if(noOneCares()) {

	toEachTheirOwn()

} else {

	beatDeadHorseInPrideAndArrogance()
} _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: WOPopUpButton
      • From: Ian Joyner <email@hidden>
References: 
 >WOPopUpButton (From: "Sigurður E. Vilhelmsson" <email@hidden>)
 >Re: WOPopUpButton (From: David LeBer <email@hidden>)
 >Re: WOPopUpButton (From: Ian Joyner <email@hidden>)
 >Re: WOPopUpButton (From: Eric Robinson <email@hidden>)
 >Re: WOPopUpButton (From: Ian Joyner <email@hidden>)

  • Prev by Date: Re: WOPopUpButton
  • Next by Date: Re: WOPopUpButton
  • Previous by thread: Re: WOPopUpButton
  • Next by thread: Re: WOPopUpButton
  • Index(es):
    • Date
    • Thread