Martin, Please see my comments below.
Martin wrote: "Well, now we're getting closer to the bone... As tools have improved I've found myself using name prefixes in fewer and fewer situations. All the IDEs I've used in the last 6 yrs can easily tell you whether something is a class or an interface, and what its parent class is. So I try and avoid embedding too much type metadata in names. I think this is the usual Java convention as well - I've never seen *any* types in the Java APIs which use these conventions." I can understand the need to be cautious about embedding too much metadata in a name. I worked with a guy that like to put all sorts of information in a file name. Something like: 20070530-Created_By_Sunburned_Surveyor_Read_Only_Peters_Computer_Backup_Directions.txt This always drove me crazy. :] Martin wrote: "<rant> I know MS popularized using I* names back in the old COM days, and I think they've propagated this into the .Net world as well. Another good reason to avoid it, IMO. Might as well use that lovely m_* convention for instance variables, not to mention prefxing every variable with a secret code word that reveals its type to those who speak Hungarian... 8^) (Luckily the inventor of this has exiled himself to far earth orbit...) </rant>" Yup. I guess I took my habit of prefixing interfaces with an the letter "I" from my days programming in Visual Basic to my Java programming. Old habits die hard... At any rate, I guess my idea of prefixing class names isn't that popular. :] What did you have in mind when you said: "Naming of methods, classes and packages is more visible (in increasing importance) - articulating some policies here might be helpful." ? Thanks, The Sunburned Surveyor Naming of methods, classes and packages is more visible (in increasing importance) - articulating some policies here might be helpful. On 5/29/07, Larry Becker <[EMAIL PROTECTED]> wrote: > Rant on Martin. > > LOL > Larry > > On 5/29/07, Martin Davis <[EMAIL PROTECTED]> wrote: > > > > > > Sunburned Surveyor wrote: > > > Martin, > > > > > > See my comments below. > > > > > > Martin wrote: "Naming of > > > methods, classes and packages is more visible (in increasing importance) > > > - articulating some policies here might be helpful." > > > > > > You make a good point here. I prefix all of my interfaces with a > > > capital "I", all of my exceptions with the prefix "Exc", and all of my > > > JUnit tests with the capital letters "JU". I'm not saying that we > > > should use this particular convention. I'm just saying that I have > > > found it helpful to distinguish interfaces, exceptions, and unit tests > > > by their class name. Perhaps we could start our coding standards with > > > a discussion of how to make this distinction. > > > > > Well, now we're getting closer to the bone... As tools have improved > > I've found myself using name prefixes in fewer and fewer situations. > > All the IDEs I've used in the last 6 yrs can easily tell you whether > > something is a class or an interface, and what its parent class is. So > > I try and avoid embedding too much type metadata in names. I think this > > is the usual Java convention as well - I've never seen *any* types in > > the Java APIs which use these conventions. > > > > <rant> > > I know MS popularized using I* names back in the old COM days, and I > > think they've propagated this into the .Net world as well. Another good > > reason to avoid it, IMO. Might as well use that lovely m_* convention > > for instance variables, not to mention prefxing every variable with a > > secret code word that reveals its type to those who speak Hungarian... > > 8^) (Luckily the inventor of this has exiled himself to far earth > orbit...) > > </rant> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > _______________________________________________ > > Jump-pilot-devel mailing list > > Jump-pilot-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > > -- > http://amusingprogrammer.blogspot.com/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
