What differentiates you as a programmer?

I have played around with LibertyBasic, I think it kinda sucks.

I tried using it before I found RealStudio (I think).

Oh, and one more for you, Oliver - learn other languages. Keep on practicing your favorite (Xojo?) but learn others too. It will make you a better programmer, learning different design patterns, different ways of doing things.

But a bit back on topic

I use

IF [NOT] <condition> THEN

depending of if TRUE or FALSE is most “readable” in context

I always put expression on same line in IF/THEN if the result is "simple

IF x>0 THEN x=x+1

I only break them up if there is complex logic following the THEN… or if ELSE is involved.
I rely on autocomplete to finish a word, but not to finish a statement (inserting THEN etc), and most times I out type autocomplete anyways so I am done before the IDE has enough time to suggest something.

For those interested BASSET is being designed to ultimated allow the creation of a program (including GUI) to be written in a dialect of BASIC and translated to SWIFT before being compiled to the target device of OSX or iOS

I agree with Gavin, over the years I have programmed in various dialects of BASIC (MBasic,QBasic,CBasic, Visual BASIC [v3 to v6], VB.NET, PL/SQL, SAS, Fortran, Cobol, PL/1, MarkIV, Rexx, Assembler, and probably a few more that I have forgotten about)

[quote=109416:@Dave S]But a bit back on topic

I use

IF [NOT] <condition> THEN

depending of if TRUE or FALSE is most “readable” in context

I always put expression on same line in IF/THEN if the result is "simple

IF x>0 THEN x=x+1

I only break them up if there is complex logic following the THEN… or if ELSE is involved.
I rely on autocomplete to finish a word, but not to finish a statement (inserting THEN etc), and most times I out type autocomplete anyways so I am done before the IDE has enough time to suggest something.

For those interested BASSET is being designed to ultimated allow the creation of a program (including GUI) to be written in a dialect of BASIC and translated to SWIFT before being compiled to the target device of OSX or iOS

I agree with Gavin, over the years I have programmed in various dialects of BASIC (MBasic,QBasic,CBasic, Visual BASIC [v3 to v6], VB.NET, PL/SQL, SAS, Fortran, Cobol, PL/1, MarkIV, Rexx, Assembler, and probably a few more that I have forgotten about)[/quote]

You might wonder why a lot of people use I,J,K for FOR/NEXT Loops?
and S for temp strings? They either once was a FORTRAN programmer, or influence by one…

  • All DIMS at the top of the Module or Method
    *parentheses for all method calls, whether there are parameters or not
    *loop counters declared as part of the loop construct
    *capitalized Class names
    *camel-cased method names
    *lower-cased keywords ’ I let Standardize Format set this
  • folders in the Navigator for Windows, Classes, graphics files etc
  • Labels that aren’t going to be changed (accessed in code) are put into a Control Set, to clean up the Navigator
  • I use a Note within Xojo as a coding diary, documenting exactly what I did during that session, plus exactly what I have to do in the next session
  • any globals are declared in a Module, as little as possible goes into App
  • properly encapsulated classes

[quote=109418:@Dave S]You might wonder why a lot of people use I,J,K for FOR/NEXT Loops?
and S for temp strings? They either once was a FORTRAN programmer, or influence by one…[/quote]
I still use for i, j, k for loop counters. I actually think it makes for clear code.

I’m afraid I really don’t like the way it formats code. All these capital letters everywhere, it doesn’t do anything for me in terms of readability. Of course, it’s subjective. I wish Standardize Format was customizable. http://www.xojonews.com/news/choose-how-to-format-your.html

Not sure, maybe my beautiful eyes and amazing hair.

I wear a red velvet smoking jacket with a yellow braid trim, whilst developing :slight_smile:

I can only program at work if I have a StarBucks coffee :slight_smile:

+1

[quote=109418:@Dave S]You might wonder why a lot of people use I,J,K for FOR/NEXT Loops?
and S for temp strings? They either once was a FORTRAN programmer[/quote]

Did not remember were i picked up i,j,k for loop variables, but i did take a Fortran (IV) course in school.

  • Karen

[quote=109394:@Oliver Scott-Brown]I googled REM and found REM in Xojo docs so I know what REM is now but thanks to those who answered anyway.

I couldn’t comprehend that Gavin actually used rem because I was in disbelief.[/quote]

REM was all the rage when I started out on the ZX spectrum. You only had to press the R key and the word REM appeared on the screen.

in fortran idents shat started with i - n were integers
dont ecall if there was something old that made i, j ,k ,l, m and n integers with only short indents allowed
:stuck_out_tongue:

Has anyone done RPG? I’ve had to maintain old code from the 70’s.

yeah that was one of the one I’d forgotten…and RAMIS… (remember a company called TRW? Thompson, Ramis and Woldridge)… one developed RAMIS (guess which one :slight_smile: ), and another developed MarkIV

HA !
At least thats a read / write language
Try APL - write once and gawd I hope you did well in the matrix math courses :slight_smile:

The only language you can truly say “its all greek to me”

The company I went to work for 10 years ago had all of their software running on an IBM System 36. All written in RPG II and III. I only go back to VB6, so I purchased some RPG II manuals off of ebay for a 1.50 and pretty much taught myself. What a PITA and lucky for me, today we rarely do anything with that machine. I’ll probably be retiring it once the next maintenance contract comes due.

I don’t think I want to look at anything earlier than RPG II.

I run my code through an obfuscater to make it MORE readable. #TheMostInterestingProgrammerInTheWorld

heh - I work here. You don’t :stuck_out_tongue:

I feel old now.

in olden days, “REM” was used to state that the current line is a REMark. and the compiler would ignore it. In todays languages, we use things like ', //, # and so forth.