And don't try coding on an iPhone with autocomplete :) Doh. Sent from my iPhone
> On 21 Dec 2013, at 20:18, Brian Leach <[email protected]> wrote: > > There are good reasons why every modern language uses mixed case. You don't > read novels in upper case and you should not read code that way. Reading is > about pattern recognition and mixed case makes for better patterning ONCE you > have adapted to it. This period of adapting is the reason why so many old > guard don't like it ! > > I have coded mixed case for decades. For steam driven systems I use a > precompiler to upper case keywords. > > You can follow conventions to ass meaning through case: Return from a GoSub > and RETURN from a Call; upper case for equated or special variables (file and > select vars); and more. > > As for searching use a decent editor. > > B > > Sent from my iPhone > >> On 21 Dec 2013, at 14:23, Doug Averch <[email protected]> wrote: >> >> "BFIND" are your really serious. Is this one of those, we must us only use >> UniBasic code? Because if it is, we U2 programmers are really dinosaurs >> not knowing the comet already has changed the world. >> >> We have been using Eclipse since 2004. The search engine is so fast and >> will search my local machine, not the database, in seconds. The Eclipse >> search engine shows not only the program but the entire line that matches. >> You can click on the line in the search window and the editor start up and >> loads the program focusing on the line in question. >> >> Gee, you should wonder how Eclipse compares to a single telnet window >> driven program written UniBasic? >> >> Regards, >> Doug >> www.u2logic.com >> "Industrial strength tools for U2 programmers and shops" >> >> >>> On Sat, Dec 21, 2013 at 6:08 AM, Symeon Breen <[email protected]> wrote: >>> >>> Not this one again .... >>> >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of Bobby Worley >>> Sent: 20 December 2013 19:02 >>> To: U2 Users List >>> Subject: [U2] BASIC code - upper, lower, CamelCase, what say you? >>> >>> First off - Merry Christmas and Happy New Year to all. >>> >>> I'm starting to write a lot of new BASIC (Universe 11.1) subroutines for >>> our >>> DesignBais application, and since I'll be starting with a blank code >>> template instead of modifying existing code, and I thought 'hey why not >>> join >>> the 21st century' and make the code look more mainstream, and readable. >>> (falling back on our last TEXMUG presentation by Clif Oliver on >>> refactoring). >>> >>> And considering Universe 11.2 now supports local subroutines and functions, >>> I should make the code look and behave more object-like. >>> >>> Does anyone know of a set of rules or guidelines on how to do this? Just >>> experimenting briefly, Universe BASIC compiler will allow any mix of cases >>> for keywords, but variables are case sensitive. Example: >>> >>>> ED BP TEST >>> ABC=1 >>> Abc=2 >>> abc=3 >>> PRINT ABC >>> Print Abc >>> pRiNt abc >>> stop >>> end >>> >>>> RUN TEST >>> 1 >>> 2 >>> 3 >>> >>> So, how are developers mixed case in their code these day? Do keywords, >>> local variables, common variable, equates follow a standard method? >>> >>> thanks in advance, >>> _______________________________________________ >>> U2-Users mailing list >>> [email protected] >>> http://listserver.u2ug.org/mailman/listinfo/u2-users >>> >>> _______________________________________________ >>> U2-Users mailing list >>> [email protected] >>> http://listserver.u2ug.org/mailman/listinfo/u2-users >> _______________________________________________ >> U2-Users mailing list >> [email protected] >> http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
