Computer Languages

High Level Languages vs Low Level "Languages" +

• Actor
• ABC
• ADA
• ADOL
• ALGOL
• APL
• ASP (VBScript, Index Server, ADO, JScript, Objects, Components)
• Assembler (x86: win32, MASM, TASM, NASM, A86, Terse, HLA. AVR, PIC, SX: Sx-Key)
• BASIC (Visual Basic, VBScript, Dartmouth Basic, CBASIC, CB-80, MBASIC, GWBASIC, STAMP)
• C/C++
• c# language +
• CA-Realizer
• Clarion
• COBOL
• xBase (dBase, FoxPro, Clipper, CodeView)
• DOS (Services, Batch)
• Eiffel
• Euphoria Multi-platform, non-limiting.
• Forth (PostScript)
• Fortran
• HTML (VRML, SGML, XML)
• Jal
• Java (JavaScript, J++, JScript)
• Lisp
• Logo
• Lotus 123 Macro
• LUA
• MetaL
• Modula-2
• Mouse
• Octave
• OpenSCAD
• Page Description (ASCII, PCL (HPGL), PostScript, pdf, IPDS)
• Paradox
• Pascal (Delphi)
• Perl
• Pilot
• PHP
• Plain English
• Procomm
• Prolog
• Pure Data (pd) +
• Python
• Rebol +
• Regular Expressions
• RPG
• Salt (telix)
• Simula
• Smalltalk
  • Squeak
• SNOBOL
• SVG
• SQL
• Terse
• WebAssembly +
• XPL0

PIC-specific languages@

SX-specifc langauges@

Libraries@ Components@ Rules@

Expression Evaluator

Books:

• coverThe Art of Computer Programming, Volumes 1..3 Boxed Set THE books! Skip college, just read this set. Not about hot topics or trendy issues, just the scientific, mathimatical, and algorithmic basis of all programming. If you don't know this stuff, you're playing. Ask the pros if they own this book.
• coverCode Complete : A Practical Handbook of Software Construction by Steve C McConnell Not language specific. Covers OOP and what and when to objectify.

On creating languages:

The easy way to do this is to use LEX and YACC, after first specifying your 'basic' grammar. YACC will spit out C code to parse your 'basic' language. You can use this code as your cross compiler which will run on windoze, Linux, etc. You also need to write the routines to perform the actions that the tokens in you grammar will cause to be called. People can kick out compilers like this in an afternoon. You get a serious compiler this way that can handle any level of parenthetical expressions.

There are good tutorials on the web. (http://epaperpress.com/lexandyacc/) The point is -- a couple of days with a book on YACC and LEX to understand it will pay off any time you have to parse something -- for the rest of your programming life.

Books:

• Unix Tool Building by Kenneth Ingham
• A Retargetable C Compiler

See also:

• https://citw.dev/tutorial/create-your-own-compiler How write your own compiler (note this produces “javascript” but that javascript might as well be assembly language for some simple processor)
  +
• http://www.labnol.org/internet/learn-coding-online/28537/ Great list of online free programming tutorials.
• Microsoft Workshop languages
• Randy Hyde's Language List (seems to be dead)
• Developer.com
• http://www.cuug.ab.ca/~wongb/funny/cpsc/shootfoot.html To Shoot Yourself In The Foot (in various languages)
• http://mindprod.com/unmain.html How To Write Unmaintainable Code (very useful to the consultant or employee who knows he is about to get the axe)
• http://goforit.unk.edu/cscourse.htm language tutorials (free)
• http://compilers.iecc.com/crenshaw/ Just an EXCELLENT tutorial by Jack W. Crenshaw
  http://www.embedded.com/staff/jackc.htm on how compilers are written. Very easy to read, very usefull, mostly complete. It has been translated to HTML and the machine code in the examples translated to x86 (while retaining the original 68000) at:
  http://crenshaw.books.myprojects.kostigoff.net
• http://michael.dipperstein.com/free.html Very nice list of free windows compilers and development related tools

The comp.compilers newsgroup, archive, links

"Every program has at least one bug and can be shortened by at least one instruction -- from which, by induction, one can deduce that every program can be reduced to one instruction which doesn't work." -- Anon.

"The most important thing in the programming language is the name. A language will not succeed without a good name. I have recently invented a very good name and now I am looking for a suitable language." -- D. E. Knuth, 1967

A computer scientist is someone who, when told to "Go to Hell," sees the "go to," rather than the destination, as harmful. -- Dr. Roger M. Firestone, rfire@cais.cais.com

Questions:

• what about PLI language from IBM 1965 ?

See also:

See:

• /techref/microchip/languages.htm
• /techref/piclist/jal/index.htm
• /techref/microchip/routines.htm
• /techref/piclist/cump/index.htm

.