Re: [U2] Mixed Case UV Basic Programming Standards.
No, I'd add punctuation, as I hinted in my email: I've hated words joined together without space or punctuation delimiters ever since. On Sun, Aug 23, 2009 at 1:01 AM, Boydell, Stuart stuart.boyd...@spotless.com.au wrote: A case of you preferring SOMETIMESLOWER perhaps? Stuart -Original Message- I like all upper case ... I don't like all lower case because there is no quick and easy way to tell if an author meant sometimes lower or sometime slower when writing sometimeslower. ** This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this communication in error, please reply to this e-mail to notify the sender of its incorrect delivery and then delete it and your reply. It is your responsibility to check this email and any attachments for viruses and defects before opening or sending them on. Spotless collects information about you to provide and market our services. For information about use, disclosure and access, see our privacy policy at http://www.spotless.com.au Please consider our environment before printing this email. ** ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
Recently spotted music compilation: WORLDSHITS ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
A case of you preferring SOMETIMESLOWER perhaps? Stuart -Original Message- I like all upper case ... I don't like all lower case because there is no quick and easy way to tell if an author meant sometimes lower or sometime slower when writing sometimeslower. ** This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this communication in error, please reply to this e-mail to notify the sender of its incorrect delivery and then delete it and your reply. It is your responsibility to check this email and any attachments for viruses and defects before opening or sending them on. Spotless collects information about you to provide and market our services. For information about use, disclosure and access, see our privacy policy at http://www.spotless.com.au Please consider our environment before printing this email. ** ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
Isn't it hard enough programming without having to find SOmeTimesSlower or SomeTImessLower or SometImesSLOwer or SomeTIMESslower or SOMETimesslower or sometimesslower or sometImesslower? I usually go with SOME.TIMES.SLOWER So often that one day just before lunch I thought to myself (and this isn't a joke) Maybe I'll go to TACO.BELL today... -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org]on Behalf Of Boydell, Stuart Sent: Sunday, August 23, 2009 1:02 AM To: louiebergsa...@gmail.com; U2 Users List Subject: Re: [U2] Mixed Case UV Basic Programming Standards. A case of you preferring SOMETIMESLOWER perhaps? Stuart -Original Message- I like all upper case ... I don't like all lower case because there is no quick and easy way to tell if an author meant sometimes lower or sometime slower when writing sometimeslower. ** This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this communication in error, please reply to this e-mail to notify the sender of its incorrect delivery and then delete it and your reply. It is your responsibility to check this email and any attachments for viruses and defects before opening or sending them on. Spotless collects information about you to provide and market our services. For information about use, disclosure and access, see our privacy policy at http://www.spotless.com.au Please consider our environment before printing this email. ** ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
I like all upper case because I believe programs should be shouted when reading aloud. I also like the comment that said it works on all platforms. And the one that said they had programs from last century. I don't like all lower case because there is no quick and easy way to tell if an author meant sometimes lower or sometime slower when writing sometimeslower. In third grade, with my first script homework assignment, I joined all my words together, because that's what my mom's writing looked like. My paper came back with about 500 red slashes, one between every word. I've hated words joined together without space or punctuation delimiters ever since. -- Louie In Seattle “It is no measure of health to be well adjusted to a profoundly sick society. -- Krishnamurti ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
sorry But I am giggling about this since after writing outside U2...I LIKE mixed case to distingush certain things... It just pisses some of the people off that I work with - because they still write ala circa 1982! -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org]on Behalf Of Dawn Wolthuis Sent: Monday, June 29, 2009 3:31 PM To: U2 Users List Subject: Re: [U2] Mixed Case UV Basic Programming Standards. Since we are writing something new, I started out with Java styling rules, then saw that the AJAX toolset was written by people more accustomed to vb styling, so there is some mishmash, but we have File Names: CamelCase Field Names: CamelCase Constants: UPPER local variables: sometimeslower otherwise lowerCamelCase verbs and other reserved words: lower This pretty much aligns with our javascript styling too. --dawn On Wed, Jun 24, 2009 at 1:38 PM, Charles Stevensonstevenson.c...@gmail.com wrote: I don't like the way I use mixed case, so it tends to evolve. Not good, because consistency in programming style throughout an application makes for easier maintenance, maintainability is the god of software quality. So I am wondering how others use mixed case. Do you capitalize/lower/mix case for commands? Operators? Variables? Equates? etc. How do you use/not use special characters in variable names? For example: readu OrderMaster from ORDER.MASTER, OrderMasterId locked ... readU OE_rec from OE_f, OE_id locked ... ReadVU OE_Date From ORDER.MASTER, OE$Id, OE$Date Locked ... READU order.master.rec( oe$date ) FROM order.master.file, order.master.id LOCKED ... That sort of thing. I hesitate to even ask this for fear of starting a war. So ground rules for this thread: 1. NOT about MERITS of Uppercase only vs. Mixed Case programming. I am only interested in answers from people who actually use mixed case. 2. NOT about GOTO. Take it outside. 3. This is about PREFERENCE, NOT SUBSTANCE. By substantive I mean rules like: - Only open a file once. - Readu should always have a locked clause. By preference I mean stuff like my example. They are all functionally equivalent. 4. NO ARGUMENTS about whether someone's style is good or bad, or yours is better. Explaining why you do it a certain way is helpful, though. Just remember, when it comes to preferences, no two programmers will agree, yet consistent style, whate'er it be, increases maintainability. Thanks, Chuck Stevenson ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Dawn M. Wolthuis Take and give some delight today ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
In message 6806801183013245804b6a7c6b34750715a...@hera.gnosys.local, phil walker p...@gnosys.co.nz writes As anyone written or thought about writing a code refactorer for U2-BASIC, this would/could/should standardize code semantics and also appearance? If this could be made configurable to the style you want to use then that would be good...and any program with a GOTO in would be deleted...without warning ;-). So any proper well-written program would get deleted without warning? :-) About the ONLY place where GOTO really is the best way of handling things is dealing with error conditions - and this is the code most programs (not only in MV) lack. Most well-written programs will contain GOTOs, to clean up the mess caused when the program trips over something the computer or user should have done and hasn't (and it's not always the programmer's fault - it could well be hardware failure, network dropped, or something stupid like that). Cheers, Wol -- Anthony W. Youngman pi...@thewolery.demon.co.uk 'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998 Visit the MaVerick web-site - http://www.maverick-dbms.org Open Source Pick ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
I started this thread and I thank those who have helped me think about it. Some good ideas there. But, hey guys, one of the thread's rules was: 2. NOT about GOTO. Take it outside. So if you don't stop, I will have to come down on this with my full authority. (My full authority consists of a polite request to change the subject line abandon this thread. Can't think of anything else.) I think all that can be said about GOTO has been said; everyone already knows every arguments on every side. If you have a standard in that regard I'm programming for you, I promise to abide by it make it work. cds ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
My standard is to coat anyone using a goto with salty duck fat drop them from 15 feet up into the play yard at the Atlanta Humane Society during Pit Bull Play Hour. To make my standard work, you'll have to learn to fly a helicopter... Given the subject, I feel compelled to add: I'm kidding. I like mixed case for readability, plus it makes the code look less Cretacious. The downside is that unless all of the legacy code has been rewritten, in order to - for example - find all of the write commands, I have to do multiple searches account for typos (Write vs write, in addition to WRITE). Not much of a downside. I use camelHump in my own stuff (great name, thanks to whoever threw it in here!). -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Charles Stevenson Sent: Monday, June 29, 2009 2:43 PM To: U2 Users List Subject: Re: [U2] Mixed Case UV Basic Programming Standards. I started this thread and I thank those who have helped me think about it. Some good ideas there. But, hey guys, one of the thread's rules was: 2. NOT about GOTO. Take it outside. So if you don't stop, I will have to come down on this with my full authority. (My full authority consists of a polite request to change the subject line abandon this thread. Can't think of anything else.) I think all that can be said about GOTO has been said; everyone already knows every arguments on every side. If you have a standard in that regard I'm programming for you, I promise to abide by it make it work. cds ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
Since we are writing something new, I started out with Java styling rules, then saw that the AJAX toolset was written by people more accustomed to vb styling, so there is some mishmash, but we have File Names: CamelCase Field Names: CamelCase Constants: UPPER local variables: sometimeslower otherwise lowerCamelCase verbs and other reserved words: lower This pretty much aligns with our javascript styling too. --dawn On Wed, Jun 24, 2009 at 1:38 PM, Charles Stevensonstevenson.c...@gmail.com wrote: I don't like the way I use mixed case, so it tends to evolve. Not good, because consistency in programming style throughout an application makes for easier maintenance, maintainability is the god of software quality. So I am wondering how others use mixed case. Do you capitalize/lower/mix case for commands? Operators? Variables? Equates? etc. How do you use/not use special characters in variable names? For example: readu OrderMaster from ORDER.MASTER, OrderMasterId locked ... readU OE_rec from OE_f, OE_id locked ... ReadVU OE_Date From ORDER.MASTER, OE$Id, OE$Date Locked ... READU order.master.rec( oe$date ) FROM order.master.file, order.master.id LOCKED ... That sort of thing. I hesitate to even ask this for fear of starting a war. So ground rules for this thread: 1. NOT about MERITS of Uppercase only vs. Mixed Case programming. I am only interested in answers from people who actually use mixed case. 2. NOT about GOTO. Take it outside. 3. This is about PREFERENCE, NOT SUBSTANCE. By substantive I mean rules like: - Only open a file once. - Readu should always have a locked clause. By preference I mean stuff like my example. They are all functionally equivalent. 4. NO ARGUMENTS about whether someone's style is good or bad, or yours is better. Explaining why you do it a certain way is helpful, though. Just remember, when it comes to preferences, no two programmers will agree, yet consistent style, whate'er it be, increases maintainability. Thanks, Chuck Stevenson ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Dawn M. Wolthuis Take and give some delight today ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
I use camel case in all the languages i program in. In unibasic i have capitalised verbs because i do not have the setting set to allow lowercase verb useage. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Charles Stevenson Sent: 24 June 2009 19:39 To: U2 Users List Subject: [U2] Mixed Case UV Basic Programming Standards. I don't like the way I use mixed case, so it tends to evolve. Not good, because consistency in programming style throughout an application makes for easier maintenance, maintainability is the god of software quality. So I am wondering how others use mixed case. Do you capitalize/lower/mix case for commands? Operators? Variables? Equates? etc. How do you use/not use special characters in variable names? For example: readu OrderMaster from ORDER.MASTER, OrderMasterId locked ... readU OE_rec from OE_f, OE_id locked ... ReadVU OE_Date From ORDER.MASTER, OE$Id, OE$Date Locked ... READU order.master.rec( oe$date ) FROM order.master.file, order.master.id LOCKED ... That sort of thing. I hesitate to even ask this for fear of starting a war. So ground rules for this thread: 1. NOT about MERITS of Uppercase only vs. Mixed Case programming. I am only interested in answers from people who actually use mixed case. 2. NOT about GOTO. Take it outside. 3. This is about PREFERENCE, NOT SUBSTANCE. By substantive I mean rules like: - Only open a file once. - Readu should always have a locked clause. By preference I mean stuff like my example. They are all functionally equivalent. 4. NO ARGUMENTS about whether someone's style is good or bad, or yours is better. Explaining why you do it a certain way is helpful, though. Just remember, when it comes to preferences, no two programmers will agree, yet consistent style, whate'er it be, increases maintainability. Thanks, Chuck Stevenson ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
Same Also leading capital letter for SubroutineLabels: No underscores, dots or other extraneous characters. File handle variables are just another variable so follow the camelCase rule but I prefix them with fv: open 'MY.FILE.NAME' to fvMyFileName Cheers, Stuart Boydell From: u2-users-boun...@listserver.u2ug.org on behalf of Larry Hiscock Sent: Thu 25/06/2009 05:05 To: 'U2 Users List' Subject: Re: [U2] Mixed Case UV Basic Programming Standards. I tend to use all lower case for verbs (e.g. read, for, loop, etc), all upper case for constants (i.e. equates -- equ TAB lit char(9)), and camel case for variables (e.g. orderMaster, customerName, etc) One advantage is that I can tell at a glance the difference between a variable and a constant. Just my $.02 Larry Hiscock Western Computer Services ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ** This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this communication in error, please reply to this e-mail to notify the sender of its incorrect delivery and then delete it and your reply. It is your responsibility to check this email and any attachments for viruses and defects before opening or sending them on. Spotless collects information about you to provide and market our services. For information about use, disclosure and access, see our privacy policy at http://www.spotless.com.au Please consider our environment before printing this email. ** ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
Does anyone else remember the days when there was only UPPER case on terminals and line printers? Our internal standard says use upper case only, we have twenty year old programs. When switching from an old program to a new one written in wobbly case you tend to miss read the code. We do have someone who is very techy that loves wobbly case, but he is just a bit strange, you know who you are.. Les Sherlock Hewkin Project Manager Group Financial Systems I.T. Department Ryehill House Ryehill Close, Lodge Way Industrial Estate, Northampton. NN5 7UA T 01604 592289 M 07917 856195 -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Boydell, Stuart Sent: 25 June 2009 07:29 To: U2 Users List Subject: Re: [U2] Mixed Case UV Basic Programming Standards. Same Also leading capital letter for SubroutineLabels: No underscores, dots or other extraneous characters. File handle variables are just another variable so follow the camelCase rule but I prefix them with fv: open 'MY.FILE.NAME' to fvMyFileName Cheers, Stuart Boydell From: u2-users-boun...@listserver.u2ug.org on behalf of Larry Hiscock Sent: Thu 25/06/2009 05:05 To: 'U2 Users List' Subject: Re: [U2] Mixed Case UV Basic Programming Standards. I tend to use all lower case for verbs (e.g. read, for, loop, etc), all upper case for constants (i.e. equates -- equ TAB lit char(9)), and camel case for variables (e.g. orderMaster, customerName, etc) One advantage is that I can tell at a glance the difference between a variable and a constant. Just my $.02 Larry Hiscock Western Computer Services ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ** This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this communication in error, please reply to this e-mail to notify the sender of its incorrect delivery and then delete it and your reply. It is your responsibility to check this email and any attachments for viruses and defects before opening or sending them on. Spotless collects information about you to provide and market our services. For information about use, disclosure and access, see our privacy policy at http://www.spotless.com.au Please consider our environment before printing this email. ** ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users html head meta http-equiv=Content-type content=text/html; charset=UTF-8 /head body P style=MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0ptSPAN style=FONT-SIZE: 8.2pt; FONT-FAMILY: 'MS Sans Serif'This e-mail and any attachments are confidential and intended solely for the use of the addressee only. If you have received this message in error, you must not copy, distribute or disclose the contents; please notify the sender immediately and delete the message. /SPAN/P P style=MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0ptSPAN style=FONT-SIZE: 8.2pt; FONT-FAMILY: 'MS Sans Serif'This message is attributed to the sender and may not necessarily reflect the view of Travis Perkins plc or its subsidiaries (Travis Perkins). Agreements binding Travis Perkins may not be concluded by means of e-mail communication. /SPAN/P P style=MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0ptSPAN style=FONT-SIZE: 8.2pt; FONT-FAMILY: 'MS Sans Serif'E-mail transmissions are not secure and Travis Perkins accepts no responsibility for changes made to this message after it was sent. Whilst steps have been taken to ensure that this message is virus free, Travis Perkins accepts no liability for infection and recommends that you scan this e-mail and any attachments. /SPAN/P P style=MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0ptSPAN style=FONT-SIZE: 8.2pt; FONT-FAMILY: 'MS Sans Serif'Part of Travis Perkins plc. Registered Office: Lodge Way House, Lodge Way, Harlestone Road, Northampton, NN5 7UG. /SPAN/P /BODY /HTML ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
Wobbly case - lol Yes i remember years ago we had a chain printer that only printed caps - we moved to a new machine and the print runs came out all funny lots of characters missing, it took us ages to figure out it was only printing the caps chars, the old machine uppercased everything in the spooler so we had to copy the spooler code over as well... -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Les Hewkin Sent: 25 June 2009 09:07 To: U2 Users List Subject: Re: [U2] Mixed Case UV Basic Programming Standards. Does anyone else remember the days when there was only UPPER case on terminals and line printers? Our internal standard says use upper case only, we have twenty year old programs. When switching from an old program to a new one written in wobbly case you tend to miss read the code. We do have someone who is very techy that loves wobbly case, but he is just a bit strange, you know who you are.. Les Sherlock Hewkin Project Manager Group Financial Systems I.T. Department Ryehill House Ryehill Close, Lodge Way Industrial Estate, Northampton. NN5 7UA T 01604 592289 M 07917 856195 -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Boydell, Stuart Sent: 25 June 2009 07:29 To: U2 Users List Subject: Re: [U2] Mixed Case UV Basic Programming Standards. Same Also leading capital letter for SubroutineLabels: No underscores, dots or other extraneous characters. File handle variables are just another variable so follow the camelCase rule but I prefix them with fv: open 'MY.FILE.NAME' to fvMyFileName Cheers, Stuart Boydell From: u2-users-boun...@listserver.u2ug.org on behalf of Larry Hiscock Sent: Thu 25/06/2009 05:05 To: 'U2 Users List' Subject: Re: [U2] Mixed Case UV Basic Programming Standards. I tend to use all lower case for verbs (e.g. read, for, loop, etc), all upper case for constants (i.e. equates -- equ TAB lit char(9)), and camel case for variables (e.g. orderMaster, customerName, etc) One advantage is that I can tell at a glance the difference between a variable and a constant. Just my $.02 Larry Hiscock Western Computer Services ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ** This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this communication in error, please reply to this e-mail to notify the sender of its incorrect delivery and then delete it and your reply. It is your responsibility to check this email and any attachments for viruses and defects before opening or sending them on. Spotless collects information about you to provide and market our services. For information about use, disclosure and access, see our privacy policy at http://www.spotless.com.au Please consider our environment before printing this email. ** ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users html head meta http-equiv=Content-type content=text/html; charset=UTF-8 /head body P style=MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0ptSPAN style=FONT-SIZE: 8.2pt; FONT-FAMILY: 'MS Sans Serif'This e-mail and any attachments are confidential and intended solely for the use of the addressee only. If you have received this message in error, you must not copy, distribute or disclose the contents; please notify the sender immediately and delete the message. /SPAN/P P style=MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0ptSPAN style=FONT-SIZE: 8.2pt; FONT-FAMILY: 'MS Sans Serif'This message is attributed to the sender and may not necessarily reflect the view of Travis Perkins plc or its subsidiaries (Travis Perkins). Agreements binding Travis Perkins may not be concluded by means of e-mail communication. /SPAN/P P style=MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0ptSPAN style=FONT-SIZE: 8.2pt; FONT-FAMILY: 'MS Sans Serif'E-mail transmissions are not secure and Travis Perkins accepts no responsibility for changes made to this message after it was sent. Whilst steps have been taken to ensure that this message is virus free, Travis Perkins accepts no liability for infection and recommends that you scan this e-mail and any attachments. /SPAN/P P style=MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0ptSPAN style=FONT-SIZE: 8.2pt; FONT-FAMILY: 'MS Sans Serif'Part of Travis Perkins plc. Registered Office: Lodge Way House, Lodge Way, Harlestone Road, Northampton, NN5 7UG. /SPAN/P /BODY /HTML ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org
Re: [U2] Mixed Case UV Basic Programming Standards.
Hi
I use mixed case using the same capitalization as for Delphi and VB (rather
than camelCase for C# and Java).
OpenSeq
NumberOfFields = DCount(SomeVariable, @FM)
However I use upper case to distinguish things that are 'special' e.g.
equate literals, file and select variables, common variables and compiler
directives. That way they stand out.
I also use upper case for STOP and the main RETURN from an external
subroutine, which helps to distinguish it from the Return from a local
GoSub.
I don't worry about searching since the editors I use are capable of
searching case-independently, and you can always write an IDescriptor to do
an UPCASE(@RECORD) if you want to search in a source file. In fact,
generally I find doing a SELECT with a LIKE clause on that is faster than
using the SEARCH command.
There should be no need to do anything special to format your comments since
any editor worth using will distinguish these (as a bare minimum). I have a
simple 'autodoc' markup in the comments that makes it easy to generate
technical docs.
So, putting it all together:
PROGRAM ShowStuff
*-
* @@Name: ShowStuff
* @@Project : Demo
* (other autodoc header info here)
*-
* @@Info{
*Shows some stuff.
*bAnd some other comments in here with HTML markups/b
* }
*-
* (other autodoc comments here: modifications, keywords, todo etc.
*-
* version stamp goes in here - assigned to a variable so it compiles into
* the object and I can then rip it from the string table.
VERDATA = Version=001002003;
VERDATA:= VerDate=12345;
VERDATA:= VerDesc=Short Description here;
(etc)
*-
$INCLUDE BOOK_TITLES.h
Open BOOK_TITLES To TITLES Else
Crt Cannot open the TITLES File
RETURN
End
Execute SSELECT BOOK_TITLES, SELECT. SLIST
Fin = @False
Loop
ReadNext TitleId From SLIST Else
Fin = @True
End
Until Fin Do
GoSub ShowISBN
Repeat
RETURN
*--
* ShowISBN: show the title id, ISBN and price
*--
ShowISBN:
Read TitleRec From TITLES,TitleId Then
Crt TitleId, TitleRecBOOK_TITLES.ISBN,
OConv(TitleRecBOOK_TITLES.PRICE,MD2)
End
Return
I find it much more legible, since I spent at least half of my life in
client languages. But I understand the point of view of those raised on
upper case only who don't use modern (grin) languages, and may initially
find it confusing. It's just a question of what you're used to.
Incidentally, this has evolved over the years. I started off upper case (no
other choice back then), went to lower case in the 'C/UNIX' age, and then
camelCase before settling on this style. When I go back to older code I can
see that this one works best.
But the main thing is to be consistent with your style and use a good
editor.
Brian
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
Of course it doesn't help the example when your mail client screws up your formatting... No, I didn't put the Loop on the same line. sigh Brian Execute SSELECT BOOK_TITLES, SELECT. SLIST Fin = @False Loop ReadNext TitleId From SLIST Else Fin = @True End Until Fin Do GoSub ShowISBN Repeat RETURN ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
An important point there from Brian on editors, yes the editors we use (no
one writes code in ed do they?) will colour highlight verbs, literals,
comments, variables etc + do case insensitive searches..
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Brian Leach
Sent: 25 June 2009 10:14
To: 'U2 Users List'
Subject: Re: [U2] Mixed Case UV Basic Programming Standards.
Hi
I use mixed case using the same capitalization as for Delphi and VB (rather
than camelCase for C# and Java).
OpenSeq
NumberOfFields = DCount(SomeVariable, @FM)
However I use upper case to distinguish things that are 'special' e.g.
equate literals, file and select variables, common variables and compiler
directives. That way they stand out.
I also use upper case for STOP and the main RETURN from an external
subroutine, which helps to distinguish it from the Return from a local
GoSub.
I don't worry about searching since the editors I use are capable of
searching case-independently, and you can always write an IDescriptor to do
an UPCASE(@RECORD) if you want to search in a source file. In fact,
generally I find doing a SELECT with a LIKE clause on that is faster than
using the SEARCH command.
There should be no need to do anything special to format your comments since
any editor worth using will distinguish these (as a bare minimum). I have a
simple 'autodoc' markup in the comments that makes it easy to generate
technical docs.
So, putting it all together:
PROGRAM ShowStuff
*-
* @@Name: ShowStuff
* @@Project : Demo
* (other autodoc header info here)
*-
* @@Info{
*Shows some stuff.
*bAnd some other comments in here with HTML markups/b
* }
*-
* (other autodoc comments here: modifications, keywords, todo etc.
*-
* version stamp goes in here - assigned to a variable so it compiles into
* the object and I can then rip it from the string table.
VERDATA = Version=001002003;
VERDATA:= VerDate=12345;
VERDATA:= VerDesc=Short Description here;
(etc)
*-
$INCLUDE BOOK_TITLES.h
Open BOOK_TITLES To TITLES Else
Crt Cannot open the TITLES File
RETURN
End
Execute SSELECT BOOK_TITLES, SELECT. SLIST
Fin = @False
Loop
ReadNext TitleId From SLIST Else
Fin = @True
End
Until Fin Do
GoSub ShowISBN
Repeat
RETURN
*--
* ShowISBN: show the title id, ISBN and price
*--
ShowISBN:
Read TitleRec From TITLES,TitleId Then
Crt TitleId, TitleRecBOOK_TITLES.ISBN,
OConv(TitleRecBOOK_TITLES.PRICE,MD2)
End
Return
I find it much more legible, since I spent at least half of my life in
client languages. But I understand the point of view of those raised on
upper case only who don't use modern (grin) languages, and may initially
find it confusing. It's just a question of what you're used to.
Incidentally, this has evolved over the years. I started off upper case (no
other choice back then), went to lower case in the 'C/UNIX' age, and then
camelCase before settling on this style. When I go back to older code I can
see that this one works best.
But the main thing is to be consistent with your style and use a good
editor.
Brian
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
Yeah, no one would be silly enough to still be using ED. Just because you can
count on it being on every client machine since it is delivered with the
standard system. Nobody could possibly be more productive in ED then any of
the color sensitive editors that may not lock records while two people are in
the same record.
From: syme...@gmail.com
To: u2-users@listserver.u2ug.org
Date: Thu, 25 Jun 2009 10:58:55 +0100
Subject: Re: [U2] Mixed Case UV Basic Programming Standards.
An important point there from Brian on editors, yes the editors we use (no
one writes code in ed do they?) will colour highlight verbs, literals,
comments, variables etc + do case insensitive searches..
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Brian Leach
Sent: 25 June 2009 10:14
To: 'U2 Users List'
Subject: Re: [U2] Mixed Case UV Basic Programming Standards.
Hi
I use mixed case using the same capitalization as for Delphi and VB (rather
than camelCase for C# and Java).
OpenSeq
NumberOfFields = DCount(SomeVariable, @FM)
However I use upper case to distinguish things that are 'special' e.g.
equate literals, file and select variables, common variables and compiler
directives. That way they stand out.
I also use upper case for STOP and the main RETURN from an external
subroutine, which helps to distinguish it from the Return from a local
GoSub.
I don't worry about searching since the editors I use are capable of
searching case-independently, and you can always write an IDescriptor to do
an UPCASE(@RECORD) if you want to search in a source file. In fact,
generally I find doing a SELECT with a LIKE clause on that is faster than
using the SEARCH command.
There should be no need to do anything special to format your comments since
any editor worth using will distinguish these (as a bare minimum). I have a
simple 'autodoc' markup in the comments that makes it easy to generate
technical docs.
So, putting it all together:
PROGRAM ShowStuff
*-
* @@Name: ShowStuff
* @@Project : Demo
* (other autodoc header info here)
*-
* @@Info{
*Shows some stuff.
*bAnd some other comments in here with HTML markups/b
* }
*-
* (other autodoc comments here: modifications, keywords, todo etc.
*-
* version stamp goes in here - assigned to a variable so it compiles into
* the object and I can then rip it from the string table.
VERDATA = Version=001002003;
VERDATA:= VerDate=12345;
VERDATA:= VerDesc=Short Description here;
(etc)
*-
$INCLUDE BOOK_TITLES.h
Open BOOK_TITLES To TITLES Else
Crt Cannot open the TITLES File
RETURN
End
Execute SSELECT BOOK_TITLES, SELECT. SLIST
Fin = @False
Loop
ReadNext TitleId From SLIST Else
Fin = @True
End
Until Fin Do
GoSub ShowISBN
Repeat
RETURN
*--
* ShowISBN: show the title id, ISBN and price
*--
ShowISBN:
Read TitleRec From TITLES,TitleId Then
Crt TitleId, TitleRecBOOK_TITLES.ISBN,
OConv(TitleRecBOOK_TITLES.PRICE,MD2)
End
Return
I find it much more legible, since I spent at least half of my life in
client languages. But I understand the point of view of those raised on
upper case only who don't use modern (grin) languages, and may initially
find it confusing. It's just a question of what you're used to.
Incidentally, this has evolved over the years. I started off upper case (no
other choice back then), went to lower case in the 'C/UNIX' age, and then
camelCase before settling on this style. When I go back to older code I can
see that this one works best.
But the main thing is to be consistent with your style and use a good
editor.
Brian
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
_
Windows Live™: Keep your life in sync.
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_BR_life_in_synch_062009
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
People use something other than ED? For the most part, all programmers
on our staff do use the ED editor but there are a few of us who like the
functions like syntax highlighting, etc. We code in all UPPER case
here. We've had programs around for 30 years so the base programs were
always uppercase and we just stuck with it over the years.
- Josh
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Symeon Breen
Sent: Thursday, June 25, 2009 5:59 AM
To: 'U2 Users List'
Subject: Re: [U2] Mixed Case UV Basic Programming Standards.
An important point there from Brian on editors, yes the editors we use
(no
one writes code in ed do they?) will colour highlight verbs, literals,
comments, variables etc + do case insensitive searches..
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Brian Leach
Sent: 25 June 2009 10:14
To: 'U2 Users List'
Subject: Re: [U2] Mixed Case UV Basic Programming Standards.
Hi
I use mixed case using the same capitalization as for Delphi and VB
(rather
than camelCase for C# and Java).
OpenSeq
NumberOfFields = DCount(SomeVariable, @FM)
However I use upper case to distinguish things that are 'special' e.g.
equate literals, file and select variables, common variables and
compiler
directives. That way they stand out.
I also use upper case for STOP and the main RETURN from an external
subroutine, which helps to distinguish it from the Return from a local
GoSub.
I don't worry about searching since the editors I use are capable of
searching case-independently, and you can always write an IDescriptor to
do
an UPCASE(@RECORD) if you want to search in a source file. In fact,
generally I find doing a SELECT with a LIKE clause on that is faster
than
using the SEARCH command.
There should be no need to do anything special to format your comments
since
any editor worth using will distinguish these (as a bare minimum). I
have a
simple 'autodoc' markup in the comments that makes it easy to generate
technical docs.
So, putting it all together:
PROGRAM ShowStuff
*-
* @@Name: ShowStuff
* @@Project : Demo
* (other autodoc header info here)
*-
* @@Info{
*Shows some stuff.
*bAnd some other comments in here with HTML markups/b
* }
*-
* (other autodoc comments here: modifications, keywords, todo etc.
*-
* version stamp goes in here - assigned to a variable so it compiles
into
* the object and I can then rip it from the string table.
VERDATA = Version=001002003;
VERDATA:= VerDate=12345;
VERDATA:= VerDesc=Short Description here;
(etc)
*-
$INCLUDE BOOK_TITLES.h
Open BOOK_TITLES To TITLES Else
Crt Cannot open the TITLES File
RETURN
End
Execute SSELECT BOOK_TITLES, SELECT. SLIST
Fin = @False
Loop
ReadNext TitleId From SLIST Else
Fin = @True
End
Until Fin Do
GoSub ShowISBN
Repeat
RETURN
*--
* ShowISBN: show the title id, ISBN and price
*--
ShowISBN:
Read TitleRec From TITLES,TitleId Then
Crt TitleId, TitleRecBOOK_TITLES.ISBN,
OConv(TitleRecBOOK_TITLES.PRICE,MD2)
End
Return
I find it much more legible, since I spent at least half of my life in
client languages. But I understand the point of view of those raised on
upper case only who don't use modern (grin) languages, and may initially
find it confusing. It's just a question of what you're used to.
Incidentally, this has evolved over the years. I started off upper case
(no
other choice back then), went to lower case in the 'C/UNIX' age, and
then
camelCase before settling on this style. When I go back to older code I
can
see that this one works best.
But the main thing is to be consistent with your style and use a good
editor.
Brian
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
Probably ot here - but i was NOT saying it was silly, I agree you can count
on ED and i do use ED / AE every day i am working on a u2 box, but when it
comes to sitting down and writing, or debugging some code i think most
people do use a more visual editor, the one that comes free with u2, (old
unidebugger or the new eclipse based one) does indeed lock the item so no
worries there.
The point I was making is that capitalising certain parts of your code is
not as necessary as it stands out anyway in a visual editor, and also that
such editors allow case insensitive searching as well.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Ron Hutchings
Sent: 25 June 2009 13:45
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Mixed Case UV Basic Programming Standards.
Yeah, no one would be silly enough to still be using ED. Just because you
can count on it being on every client machine since it is delivered with the
standard system. Nobody could possibly be more productive in ED then any of
the color sensitive editors that may not lock records while two people are
in the same record.
From: syme...@gmail.com
To: u2-users@listserver.u2ug.org
Date: Thu, 25 Jun 2009 10:58:55 +0100
Subject: Re: [U2] Mixed Case UV Basic Programming Standards.
An important point there from Brian on editors, yes the editors we use (no
one writes code in ed do they?) will colour highlight verbs, literals,
comments, variables etc + do case insensitive searches..
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Brian Leach
Sent: 25 June 2009 10:14
To: 'U2 Users List'
Subject: Re: [U2] Mixed Case UV Basic Programming Standards.
Hi
I use mixed case using the same capitalization as for Delphi and VB
(rather
than camelCase for C# and Java).
OpenSeq
NumberOfFields = DCount(SomeVariable, @FM)
However I use upper case to distinguish things that are 'special' e.g.
equate literals, file and select variables, common variables and compiler
directives. That way they stand out.
I also use upper case for STOP and the main RETURN from an external
subroutine, which helps to distinguish it from the Return from a local
GoSub.
I don't worry about searching since the editors I use are capable of
searching case-independently, and you can always write an IDescriptor to
do
an UPCASE(@RECORD) if you want to search in a source file. In fact,
generally I find doing a SELECT with a LIKE clause on that is faster than
using the SEARCH command.
There should be no need to do anything special to format your comments
since
any editor worth using will distinguish these (as a bare minimum). I have
a
simple 'autodoc' markup in the comments that makes it easy to generate
technical docs.
So, putting it all together:
PROGRAM ShowStuff
*-
* @@Name: ShowStuff
* @@Project : Demo
* (other autodoc header info here)
*-
* @@Info{
*Shows some stuff.
*bAnd some other comments in here with HTML markups/b
* }
*-
* (other autodoc comments here: modifications, keywords, todo etc.
*-
* version stamp goes in here - assigned to a variable so it compiles into
* the object and I can then rip it from the string table.
VERDATA = Version=001002003;
VERDATA:= VerDate=12345;
VERDATA:= VerDesc=Short Description here;
(etc)
*-
$INCLUDE BOOK_TITLES.h
Open BOOK_TITLES To TITLES Else
Crt Cannot open the TITLES File
RETURN
End
Execute SSELECT BOOK_TITLES, SELECT. SLIST
Fin = @False
Loop
ReadNext TitleId From SLIST Else
Fin = @True
End
Until Fin Do
GoSub ShowISBN
Repeat
RETURN
*--
* ShowISBN: show the title id, ISBN and price
*--
ShowISBN:
Read TitleRec From TITLES,TitleId Then
Crt TitleId, TitleRecBOOK_TITLES.ISBN,
OConv(TitleRecBOOK_TITLES.PRICE,MD2)
End
Return
I find it much more legible, since I spent at least half of my life in
client languages. But I understand the point of view of those raised on
upper case only who don't use modern (grin) languages, and may initially
find it confusing. It's just a question of what you're used to.
Incidentally, this has evolved over the years. I started off upper case
(no
other choice back then), went to lower case in the 'C/UNIX' age, and then
camelCase before settling on this style. When I go back to older code I
can
see that this one works best
Re: [U2] Mixed Case UV Basic Programming Standards.
You're probably right about ED. After all, EDLIN is probably still lurking somewhere in the belly of all that Windows flash and dazzle. Lowest common denominator and all that... After 16 years in the MV world, I've never really learned ED, because I was introduced to Pick/D3 and SB+ at the same time. Since I came to this environment after 9 years on a Wang VS with its modeless editor, SE was the most natural thing to use, and I still do, although I now prefer AccuTerm's WED. Norman Morgan nmor...@brake.com http://www.brake.com Children seldom misquote you. In fact, they usually repeat word for word what you shouldn't have said. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Ron Hutchings Sent: Thursday, June 25, 2009 7:45 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Mixed Case UV Basic Programming Standards. Yeah, no one would be silly enough to still be using ED. Just because you can count on it being on every client machine since it is delivered with the standard system. Nobody could possibly be more productive in ED then any of the color sensitive editors that may not lock records while two people are in the same record. From: syme...@gmail.com To: u2-users@listserver.u2ug.org Date: Thu, 25 Jun 2009 10:58:55 +0100 Subject: Re: [U2] Mixed Case UV Basic Programming Standards. An important point there from Brian on editors, yes the editors we use (no one writes code in ed do they?) will colour highlight verbs, literals, comments, variables etc + do case insensitive searches.. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
I didn't know how lucky I was being able to use Brian's MVDeveloper to
code with. I had become dependant on it. It was a great time saver. I
am now working on Univision and using ED, all the programs are in
upper case which I don't mind, but there is no indentation and there
are many statements on one line. The code was last amended around 1984
when GOTO was common practice and GOSUB's with GOSUBS etc. I have had
to purchase Textpad so I can have all the niceties of MVDeveloper.
Kishor Parmar
Quoting Joshua Gallant jgall...@cbd.com:
People use something other than ED? For the most part, all programmers
on our staff do use the ED editor but there are a few of us who like the
functions like syntax highlighting, etc. We code in all UPPER case
here. We've had programs around for 30 years so the base programs were
always uppercase and we just stuck with it over the years.
- Josh
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Symeon Breen
Sent: Thursday, June 25, 2009 5:59 AM
To: 'U2 Users List'
Subject: Re: [U2] Mixed Case UV Basic Programming Standards.
An important point there from Brian on editors, yes the editors we use
(no
one writes code in ed do they?) will colour highlight verbs, literals,
comments, variables etc + do case insensitive searches..
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Brian Leach
Sent: 25 June 2009 10:14
To: 'U2 Users List'
Subject: Re: [U2] Mixed Case UV Basic Programming Standards.
Hi
I use mixed case using the same capitalization as for Delphi and VB
(rather
than camelCase for C# and Java).
OpenSeq
NumberOfFields = DCount(SomeVariable, @FM)
However I use upper case to distinguish things that are 'special' e.g.
equate literals, file and select variables, common variables and
compiler
directives. That way they stand out.
I also use upper case for STOP and the main RETURN from an external
subroutine, which helps to distinguish it from the Return from a local
GoSub.
I don't worry about searching since the editors I use are capable of
searching case-independently, and you can always write an IDescriptor to
do
an UPCASE(@RECORD) if you want to search in a source file. In fact,
generally I find doing a SELECT with a LIKE clause on that is faster
than
using the SEARCH command.
There should be no need to do anything special to format your comments
since
any editor worth using will distinguish these (as a bare minimum). I
have a
simple 'autodoc' markup in the comments that makes it easy to generate
technical docs.
So, putting it all together:
PROGRAM ShowStuff
*-
* @@Name: ShowStuff
* @@Project : Demo
* (other autodoc header info here)
*-
* @@Info{
*Shows some stuff.
*bAnd some other comments in here with HTML markups/b
* }
*-
* (other autodoc comments here: modifications, keywords, todo etc.
*-
* version stamp goes in here - assigned to a variable so it compiles
into
* the object and I can then rip it from the string table.
VERDATA = Version=001002003;
VERDATA:= VerDate=12345;
VERDATA:= VerDesc=Short Description here;
(etc)
*-
$INCLUDE BOOK_TITLES.h
Open BOOK_TITLES To TITLES Else
Crt Cannot open the TITLES File
RETURN
End
Execute SSELECT BOOK_TITLES, SELECT. SLIST
Fin = @False
Loop
ReadNext TitleId From SLIST Else
Fin = @True
End
Until Fin Do
GoSub ShowISBN
Repeat
RETURN
*--
* ShowISBN: show the title id, ISBN and price
*--
ShowISBN:
Read TitleRec From TITLES,TitleId Then
Crt TitleId, TitleRecBOOK_TITLES.ISBN,
OConv(TitleRecBOOK_TITLES.PRICE,MD2)
End
Return
I find it much more legible, since I spent at least half of my life in
client languages. But I understand the point of view of those raised on
upper case only who don't use modern (grin) languages, and may initially
find it confusing. It's just a question of what you're used to.
Incidentally, this has evolved over the years. I started off upper case
(no
other choice back then), went to lower case in the 'C/UNIX' age, and
then
camelCase before settling on this style. When I go back to older code I
can
see that this one works best.
But the main thing is to be consistent with your style and use a good
editor.
Brian
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
For editing, I am happy using UltraEdit from IDMcomp.com. You can choose color
coded syntax to be BASIC - Universe from the view menu. Easy to use; it is a
full screen editor with ftp abilities. Currently UltraEdit alone is priced at
$49.95. IDM's UltraCompare adds another phenomenal tool to your arsenal. If you
ever want to know what changed in code from this version to that, from one
customer to another, this really helps.
Talk to Susan if you use PRC, I beleve she says they play together nicely.
Date: Thu, 25 Jun 2009 15:53:03 +0100
From: kis...@parmars.com
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Mixed Case UV Basic Programming Standards.
I didn't know how lucky I was being able to use Brian's MVDeveloper to
code with. I had become dependant on it. It was a great time saver. I
am now working on Univision and using ED, all the programs are in
upper case which I don't mind, but there is no indentation and there
are many statements on one line. The code was last amended around 1984
when GOTO was common practice and GOSUB's with GOSUBS etc. I have had
to purchase Textpad so I can have all the niceties of MVDeveloper.
Kishor Parmar
Quoting Joshua Gallant jgall...@cbd.com:
People use something other than ED? For the most part, all programmers
on our staff do use the ED editor but there are a few of us who like the
functions like syntax highlighting, etc. We code in all UPPER case
here. We've had programs around for 30 years so the base programs were
always uppercase and we just stuck with it over the years.
- Josh
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Symeon Breen
Sent: Thursday, June 25, 2009 5:59 AM
To: 'U2 Users List'
Subject: Re: [U2] Mixed Case UV Basic Programming Standards.
An important point there from Brian on editors, yes the editors we use
(no
one writes code in ed do they?) will colour highlight verbs, literals,
comments, variables etc + do case insensitive searches..
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Brian Leach
Sent: 25 June 2009 10:14
To: 'U2 Users List'
Subject: Re: [U2] Mixed Case UV Basic Programming Standards.
Hi
I use mixed case using the same capitalization as for Delphi and VB
(rather
than camelCase for C# and Java).
OpenSeq
NumberOfFields = DCount(SomeVariable, @FM)
However I use upper case to distinguish things that are 'special' e.g.
equate literals, file and select variables, common variables and
compiler
directives. That way they stand out.
I also use upper case for STOP and the main RETURN from an external
subroutine, which helps to distinguish it from the Return from a local
GoSub.
I don't worry about searching since the editors I use are capable of
searching case-independently, and you can always write an IDescriptor to
do
an UPCASE(@RECORD) if you want to search in a source file. In fact,
generally I find doing a SELECT with a LIKE clause on that is faster
than
using the SEARCH command.
There should be no need to do anything special to format your comments
since
any editor worth using will distinguish these (as a bare minimum). I
have a
simple 'autodoc' markup in the comments that makes it easy to generate
technical docs.
So, putting it all together:
PROGRAM ShowStuff
*-
* @@Name : ShowStuff
* @@Project : Demo
* (other autodoc header info here)
*-
* @@Info{
* Shows some stuff.
* bAnd some other comments in here with HTML markups/b
* }
*-
* (other autodoc comments here: modifications, keywords, todo etc.
*-
* version stamp goes in here - assigned to a variable so it compiles
into
* the object and I can then rip it from the string table.
VERDATA = Version=001002003;
VERDATA:= VerDate=12345;
VERDATA:= VerDesc=Short Description here;
(etc)
*-
$INCLUDE BOOK_TITLES.h
Open BOOK_TITLES To TITLES Else
Crt Cannot open the TITLES File
RETURN
End
Execute SSELECT BOOK_TITLES, SELECT. SLIST
Fin = @False
Loop
ReadNext TitleId From SLIST Else
Fin = @True
End
Until Fin Do
GoSub ShowISBN
Repeat
RETURN
*--
* ShowISBN: show the title id, ISBN and price
*--
ShowISBN:
Read TitleRec From TITLES,TitleId Then
Crt TitleId, TitleRecBOOK_TITLES.ISBN,
OConv
[U2] Mixed Case UV Basic Programming Standards.
I don't like the way I use mixed case, so it tends to evolve. Not good, because consistency in programming style throughout an application makes for easier maintenance, maintainability is the god of software quality. So I am wondering how others use mixed case. Do you capitalize/lower/mix case for commands? Operators? Variables? Equates? etc. How do you use/not use special characters in variable names? For example: readu OrderMaster from ORDER.MASTER, OrderMasterId locked ... readU OE_rec from OE_f, OE_id locked ... ReadVU OE_Date From ORDER.MASTER, OE$Id, OE$Date Locked ... READU order.master.rec( oe$date ) FROM order.master.file, order.master.id LOCKED ... That sort of thing. I hesitate to even ask this for fear of starting a war. So ground rules for this thread: 1. NOT about MERITS of Uppercase only vs. Mixed Case programming. I am only interested in answers from people who actually use mixed case. 2. NOT about GOTO. Take it outside. 3. This is about PREFERENCE, NOT SUBSTANCE. By substantive I mean rules like: - Only open a file once. - Readu should always have a locked clause. By preference I mean stuff like my example. They are all functionally equivalent. 4. NO ARGUMENTS about whether someone's style is good or bad, or yours is better. Explaining why you do it a certain way is helpful, though. Just remember, when it comes to preferences, no two programmers will agree, yet consistent style, whate'er it be, increases maintainability. Thanks, Chuck Stevenson ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
one drawback I see is that you could get into some trouble with the Capitalize each word. (far fetched example:) RedOmen = 1 RedoMen = 2 Even though they will be unique variable names, they consist of the same sequence of letters REDOMEN Keeping it to Redomen (no capitalization after the first letter) would avoid it. Personally, I've been coding in UPPER for too many years, and lowercase coding just looks strange to mebut as I program in more and more (perl, javascript, etc..) that use lowercase as the norm, then lower case in UV would look normal. George For example: readu OrderMaster from ORDER.MASTER, OrderMasterId locked ... readU OE_rec from OE_f, OE_id locked ... ReadVU OE_Date From ORDER.MASTER, OE$Id, OE$Date Locked ... READU order.master.rec( oe$date ) FROM order.master.file, ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
I tend to use all lower case for verbs (e.g. read, for, loop, etc), all upper case for constants (i.e. equates -- equ TAB lit char(9)), and camel case for variables (e.g. orderMaster, customerName, etc) One advantage is that I can tell at a glance the difference between a variable and a constant. Just my $.02 Larry Hiscock Western Computer Services ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
I use all caps except for comments and tags. Comments follow normal proper English capitalization and tags are TitleCase with no spaces. I find that this convention, along with good color choices for the syntax highlighting in AccuTerm's WED editor makes my code easy to read. Norman Morgan nmor...@brake.com http://www.brake.com Elect NO incumbents -- throw ALL the rascals out. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Charles Stevenson Sent: Wednesday, June 24, 2009 1:39 PM To: U2 Users List Subject: [U2] Mixed Case UV Basic Programming Standards. I don't like the way I use mixed case, so it tends to evolve. Not good, because consistency in programming style throughout an application makes for easier maintenance, maintainability is the god of software quality. So I am wondering how others use mixed case. Do you capitalize/lower/mix case for commands? Operators? Variables? Equates? etc. How do you use/not use special characters in variable names? For example: readu OrderMaster from ORDER.MASTER, OrderMasterId locked ... readU OE_rec from OE_f, OE_id locked ... ReadVU OE_Date From ORDER.MASTER, OE$Id, OE$Date Locked ... READU order.master.rec( oe$date ) FROM order.master.file, order.master.id LOCKED ... That sort of thing. I hesitate to even ask this for fear of starting a war. So ground rules for this thread: 1. NOT about MERITS of Uppercase only vs. Mixed Case programming. I am only interested in answers from people who actually use mixed case. 2. NOT about GOTO. Take it outside. 3. This is about PREFERENCE, NOT SUBSTANCE. By substantive I mean rules like: - Only open a file once. - Readu should always have a locked clause. By preference I mean stuff like my example. They are all functionally equivalent. 4. NO ARGUMENTS about whether someone's style is good or bad, or yours is better. Explaining why you do it a certain way is helpful, though. Just remember, when it comes to preferences, no two programmers will agree, yet consistent style, whate'er it be, increases maintainability. Thanks, Chuck Stevenson ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
I tend to lowercase commands and labels. I only UPCASE variables, file variables, and constants. - CHARLES I Tend to Be Variable BAROUCH ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
Almost the same, With addition of : - Pascal case ( upper case for 1st character ) for function/subroutine arguments - UPPER CASE for file variables -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of Larry Hiscock Sent: June 24, 2009 3:06 PM To: 'U2 Users List' Subject: Re: [U2] Mixed Case UV Basic Programming Standards. I tend to use all lower case for verbs (e.g. read, for, loop, etc), all upper case for constants (i.e. equates -- equ TAB lit char(9)), and camel case for variables (e.g. orderMaster, customerName, etc) One advantage is that I can tell at a glance the difference between a variable and a constant. Just my $.02 Larry Hiscock Western Computer Services ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
I use all upper case for everything except comments. This ensures that if I am looking for code via an ESEARCH, I will have a better chance to find it. Some of my tools don't case, but some do. It will also be backward compatible. John Israel Sr. Programmer/Analyst Dayton Superior Corporation 721 Richard St. Dayton, OH 45342 937-866-0711 x44380 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
Code in uppercase and mixed case for Comments, displayed messages/queries, and error messages. Jerry Banker -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Charles Stevenson Sent: Wednesday, June 24, 2009 1:39 PM To: U2 Users List Subject: [U2] Mixed Case UV Basic Programming Standards. I don't like the way I use mixed case, so it tends to evolve. Not good, because consistency in programming style throughout an application makes for easier maintenance, maintainability is the god of software quality. So I am wondering how others use mixed case. Do you capitalize/lower/mix case for commands? Operators? Variables? Equates? etc. How do you use/not use special characters in variable names? For example: readu OrderMaster from ORDER.MASTER, OrderMasterId locked ... readU OE_rec from OE_f, OE_id locked ... ReadVU OE_Date From ORDER.MASTER, OE$Id, OE$Date Locked ... READU order.master.rec( oe$date ) FROM order.master.file, order.master.id LOCKED ... That sort of thing. I hesitate to even ask this for fear of starting a war. So ground rules for this thread: 1. NOT about MERITS of Uppercase only vs. Mixed Case programming. I am only interested in answers from people who actually use mixed case. 2. NOT about GOTO. Take it outside. 3. This is about PREFERENCE, NOT SUBSTANCE. By substantive I mean rules like: - Only open a file once. - Readu should always have a locked clause. By preference I mean stuff like my example. They are all functionally equivalent. 4. NO ARGUMENTS about whether someone's style is good or bad, or yours is better. Explaining why you do it a certain way is helpful, though. Just remember, when it comes to preferences, no two programmers will agree, yet consistent style, whate'er it be, increases maintainability. Thanks, Chuck Stevenson ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
Oh, you didNot say GOTO... -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Charles Stevenson Sent: Wednesday, June 24, 2009 2:39 PM To: U2 Users List Subject: [U2] Mixed Case UV Basic Programming Standards. I don't like the way I use mixed case, so it tends to evolve. Not good, because consistency in programming style throughout an application makes for easier maintenance, maintainability is the god of software quality. So I am wondering how others use mixed case. Do you capitalize/lower/mix case for commands? Operators? Variables? Equates? etc. How do you use/not use special characters in variable names? For example: readu OrderMaster from ORDER.MASTER, OrderMasterId locked ... readU OE_rec from OE_f, OE_id locked ... ReadVU OE_Date From ORDER.MASTER, OE$Id, OE$Date Locked ... READU order.master.rec( oe$date ) FROM order.master.file, order.master.id LOCKED ... That sort of thing. I hesitate to even ask this for fear of starting a war. So ground rules for this thread: 1. NOT about MERITS of Uppercase only vs. Mixed Case programming. I am only interested in answers from people who actually use mixed case. 2. NOT about GOTO. Take it outside. 3. This is about PREFERENCE, NOT SUBSTANCE. By substantive I mean rules like: - Only open a file once. - Readu should always have a locked clause. By preference I mean stuff like my example. They are all functionally equivalent. 4. NO ARGUMENTS about whether someone's style is good or bad, or yours is better. Explaining why you do it a certain way is helpful, though. Just remember, when it comes to preferences, no two programmers will agree, yet consistent style, whate'er it be, increases maintainability. Thanks, Chuck Stevenson ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
As anyone written or thought about writing a code refactorer for U2-BASIC, this would/could/should standardize code semantics and also appearance? If this could be made configurable to the style you want to use then that would be good...and any program with a GOTO in would be deleted...without warning ;-). -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of Dan Fitzgerald Sent: Thursday, 25 June 2009 8:45 a.m. To: 'U2 Users List' Subject: Re: [U2] Mixed Case UV Basic Programming Standards. Oh, you didNot say GOTO... -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Charles Stevenson Sent: Wednesday, June 24, 2009 2:39 PM To: U2 Users List Subject: [U2] Mixed Case UV Basic Programming Standards. I don't like the way I use mixed case, so it tends to evolve. Not good, because consistency in programming style throughout an application makes for easier maintenance, maintainability is the god of software quality. So I am wondering how others use mixed case. Do you capitalize/lower/mix case for commands? Operators? Variables? Equates? etc. How do you use/not use special characters in variable names? For example: readu OrderMaster from ORDER.MASTER, OrderMasterId locked ... readU OE_rec from OE_f, OE_id locked ... ReadVU OE_Date From ORDER.MASTER, OE$Id, OE$Date Locked ... READU order.master.rec( oe$date ) FROM order.master.file, order.master.id LOCKED ... That sort of thing. I hesitate to even ask this for fear of starting a war. So ground rules for this thread: 1. NOT about MERITS of Uppercase only vs. Mixed Case programming. I am only interested in answers from people who actually use mixed case. 2. NOT about GOTO. Take it outside. 3. This is about PREFERENCE, NOT SUBSTANCE. By substantive I mean rules like: - Only open a file once. - Readu should always have a locked clause. By preference I mean stuff like my example. They are all functionally equivalent. 4. NO ARGUMENTS about whether someone's style is good or bad, or yours is better. Explaining why you do it a certain way is helpful, though. Just remember, when it comes to preferences, no two programmers will agree, yet consistent style, whate'er it be, increases maintainability. Thanks, Chuck Stevenson ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
I remember seeing functionality in Microsoft Visual Studio that allowed for eight or ten different coding styles, switchable on the fly, useful for programmers working in teams. --Bill ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Mixed Case UV Basic Programming Standards.
I prefer and use lower case statements/functions/labels, etc and variables in uppercase. Purely to be consistent, all existing code is coded in the style - layout, format, case of the original. Nothing worse than seeing different standards in the one program. ;) It makes good sense for someone coding in .NET to use something they're familiar with. However, if it is maintained by traditional U2 programmers it can case some serious issues on some U2/MV platforms (or simply won't work 'as expected')...YMMV... Issues with mixed/lowercase: - lack of cross-platform consistent support for mixed-case. All platforms support uppercase everything...keeps it simple. - backward compatibility to earlier U2 release - old UV releases have limited mix-case support. - some platforms variables names are case-sensitive (a nightmare to debug, if variable Abc and ABc is different) - third-party IDE/editor support. Sometimes, mixed case just won't work (code folding, syntax colouring, auto-indenting, code-completion, etc)...usually nothing you can't hand fix. Although all uppercase is less readable and less pretty (to an extent) it is easier to maintain as a single standard. As you will always come across people deadest against any such change. And if you want to maintain a consistent standard all your code is already 100% in uppercase, it is best to leave it as is. :) -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Charles Stevenson Sent: Thursday, 25 June 2009 4:39 AM To: U2 Users List Subject: [U2] Mixed Case UV Basic Programming Standards. I don't like the way I use mixed case, so it tends to evolve. Not good, because consistency in programming style throughout an application makes for easier maintenance, maintainability is the god of software quality. So I am wondering how others use mixed case. Do you capitalize/lower/mix case for commands? Operators? Variables? Equates? etc. How do you use/not use special characters in variable names? users ** IMPORTANT MESSAGE * This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. ** ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
