Just a reminder for UniData users using mixed case, you may need to consider compiling with the -I flag (Case Insensitive Keywords allowed) We were getting some syntax errors on programs that were using SB+ SQL commands, until we started compiling with this flag. (Ironically the flag is in upper case :-) ) You may want to read up on this flag.
In reference to code not compiling, did you try reformatting your source code, before compiling? (Using the AE editor, 'FORMAT' command) This usually converts control characters to spaces. We had an issue years ago, that core dumped on an old RS/6000 every time we compiled a program that contained tabs in the source. UniData may have corrected this 'feature', though. Hope that helps. -Phil- -----Original Message----- From: Brian Leach [mailto:[EMAIL PROTECTED] Sent: Saturday, March 08, 2008 7:07 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] blank lines in code / mixed case Dennis I have no idea why your code should not compile ... I always use plenty of whitespace and, yes, for the past 15+ years I've been using mixed case. For good reasons - once you get used to ie (and that *IS* the caveat) it's much quicker to scan. That's why all modern languages use it. Of course, people who haven't taken time to get used to it, or don't use the huge number of client or web languages that use mixed case, don't see the benefit. If you're coming from an upper case only environment, you need time to train your brain to read it. Mixed casing has been on UniVerse since the year dot whereas UniData has only just emerged from the stone age on this one. Personally, since I spend much of my time in C#, Delphi, VB, PHP. mvScript etc. I much prefer to read: Fin = @False Loop ReadNext CustId Else Fin = @True Until Fin Do ReadU CustomerRec From CUSTOMER.F, CustId Then GoSub CalculateOrderTotal End Else Release CUSTOMER.F, CustId End Repeat RETURN Than: FIN = 0 LOOP READNEXT CUSTID ELSE FIN = 0 UNTIL FIN DO READU CUSTOMERREC FROM CUSTOMER.F, CUSTID THEN GOSUB 1000 END ELSE RELEASE CUSTOMER.F,CUSTID END REPEAT RETURN As I say, it's partly what you're used to and what you're prepared to learn. But there is another important argument: what the rest of the world is used to. Every other language in popular use today uses mixed case. Part of what I try to do - through the U2UG, training, articles etc - is to present U2 as a modern business platform. Anything that *looks* old, however effective, makes that more difficult and it is in all our interests to keep pushing that message. Now, I'm not suggesting that you convert any old code to mixed case, or that you start to insert mixed case into existing code. But for new ventures, it makes sense to work with what has been frequently proven to be best. I know we like to live in a technology bubble, but there are things we can learn from the rest of the industry. Regards Brian > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Dennis Bartlett > Sent: 08 March 2008 10:18 > To: u2-users@listserver.u2ug.org > Subject: [U2] blank lines in code / mixed case > > How come my code won't compile if there are blank lines in > it? And yet when I find source on the net it has blank lines in it? > > and while we're at it, what is the case for / against using > lower or upper case code, and what do I need to set to allow > this to happen? > > Thanks > ------- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/