Re: [U2] BASIC code - upper, lower, CamelCase, what say you?

Wonder if anyone has ever done a study on whether by using U/l variables, now you will be hitting the shift
a whole lot more, does this lead to or worsen carpel tunnel?   Kind of a serious concern.....
 
I think it also makes debugging more difficult, I'd rather stick to all UPPER or all lower Nothing better
Than wasting 2 hours going through a program to find out Oops, mean L instead of l

George

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Bobby Worley
Sent: Friday, December 20, 2013 2:32 PM
To: U2 Users List
Subject: Re: [U2] BASIC code - upper, lower, CamelCase, what say you?

This is really what got my thought-process flowing on this subject.  I saw
this code on github after the Rocket Software "Whats New in 11.2" webinar:

https://github.com/RocketSoftware/u2-servers-lab/blob/master/UniVerse-11.2/Local/BP/LocalMain

PROGRAM LocalMain
    ** Let's have a quick look at local scoping

    CRT "Calling the local SUBROUTINE"
    CALL Main(@SENTENCE) ;* This will call Main() below, rather than
an external subroutine
    CRT "Back from the local SUBROUTINE"

END

SUBROUTINE Main(Args)
    CRT "Running inside the local SUBROUTINE"
    CRT "Args:" :Args

    FOR Counter = 1 TO 3
        CALL InnerLoop(Counter)
    NEXT Counter
RETURN

SUBROUTINE InnerLoop(OutsideCounter)
    * Notice this won't affect Main()'s 'Counter' variable due to scoping
    FOR Counter = 1 TO OutsideCounter
        CRT "*":

    NEXT Counter
    CRT
RETURN
_______________________________________________
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