QNial programming language - Howell's

Table of Contents :


The QNial programming language - a short description

"... QNial is the child of a beautiful marriage between the LISP and APL programming languages. ..." That's how I tend to see QNial. Many times I've left her, only to come back again out of frustration with other languages. dfhhsrtj Of course, one does have to work with other languages depending on the project, which is also a good thing as there is a lot to learn out there, which also provides occasional ideas for the QNial capabilities that I build.

Bash scripting and QNial - a great hybrid programming environment

Bash regular expression capabilities, and the enormous [number, diversity, power, speed] of Unix commands, along with the QNial "host" command to run shell programs, make for an awesome preferred programming environment for me. Obviously I'm not big on [windows, GUI interfaces, etc] as I do not create user applications. To get my work done [quick, efficient]ly, I avoid all that stuff as much as possible, so I use the terminal. I extensively use Unix [grep, sed], but not awk and many other great tools. As for awk, I always get the impression that QNial-native is the best approach, but I'm sure that some situations woud benefit. I'm pretty sure that I will not take the time to learn awk in the future? A big disadvantage of the [QNial, bash, Unix command] hybrid is that my coding is often operating system dependent. I'm fine with that, as my programs aren't targeted to others. So why don't I use Python? Whatever - the devil you [know, like]... I have not compiled QNial with it's regular expression capabilities (as provided), but now that I am far more comfortable with a hybrid of [QNial, bash scripts], there isn't quite the same incentive to go back and re-compile. (... I'm lazy)

List of Howell's QNial [ndf files, operators]

The operators, and at time special data, are extracted from my Qnial directory with a simple bash script that takes advantage of my simple formatting convention for ndf files. Click to see the almost-full list. The list is currently far from complete, as I have not put the formatting in all ndf files, but at least almost-all files are listed. Some files are still in directories other than QNial, but I now try to minimize that for simplicity and tracking. Note that not all operators are of my own creation, but were provided with the standard QNial package. I have [modified, augmented] a few of those. Fileops.ndf and strings.ndf are good examples. A near-full list of my bash scripts is also available (see also my Linux [command, script] web-page).

Selected list of Howell's major QNial programming projects

Augmented [strings.ndf, fileops.ndf] operators - I've added many operators that have come ijn handy for my for my [work, projects].

Debugging, tracking loaddefs, etc

I use the following flags often. They are defined in "setup.ndf" so are available throughout my QNial programs. flag_break := o ; % stop execution to test an operator or the local environment ; flag_debug := o ; % include additional output to help track where loaddef errors occur ; Additionally, several "special" flags are use in files, such as : flag_check := o ; % force checking of all operators with examples, showing results ; flag_paren := o ; % used for ; Generally these are implemented as conditionals, such as : IF flag_break = l THEN Break ; ENDIF ; IF flag_debug = l THEN write 'loading point in program>' ; ENDIF ; IF flag_print = l THEN <... coding for printout ...> ; ENDIF ; At any time, the programmer can set the flags to o or l to control the information. Faults occur normally during searches, and most often (for me anyways) these must not stop execution! This is set in setup.ndf. settrigger o ; The QNial "watch" operator provides awesome QNial debugging power!! X gets count 5; watch !x 'write ''X changed to: '' X'

"Text [self, external] % similarity" versus "Plagiarism"

?????2020 initial posting