A brief History

[Aurel]

-

[Charles Pegge]

The fusion of Basic, Assembler, and C notation is intentional, and works rather well without the necessity of language block switches. I have often been tempted to add LISP syntax as well. It's technically possible but might be taking things a bit too far

However, we do have switches for controlling case-sensitivity, auto-dim and name-redefinition.

The logical operators are going to be very useful, especially when porting in C-code.

[edcronos]

Aurel
I'm waiting for the new version,
I get vices very easily and I have difficulty decorating words,

so I practically only use if's loops and arrays, even the "Do Loops" I forget how to write and use, and I end up using the same conditional Goto,
it's usually easier for me to create a new function than to remember the name and syntax of one that does what I want. even variable names I usually use only 3 letters

Code: [Select]

               If Loi = OLi Or Loi = OLf Then
                    T = 1
                    If Oquadante_L = True Then GoSub OCoL: If T = 1 Then OLf = OLf + OqL: OLi = OLi + OqL: T = 0: Loi = Loi + OqL
                    '  If OZig_LN = 4 Then
                    Lig = Lig * -1: Loi = Loi + Lig
                    '    Else
                    ' OZig_LN = OZig_LN + 1
                    '  End If
               End If
          End If
part of one of the first routines I did in vba after I related to Basic, nowadays I already know how to use functions

I've been reprimanded a lot about it, but when I'm writing something, I do not think much, I get the idea, I think about the logic and I write
and variable types are an important part of the good functioning of routines
so my early warning of the correct use


Charles Pegge
Wow, lisp?
I imagine the knot that should give in the head of one who knows more than one language,
I think without delimiters it should create many programming vices and disrupt those who are learning, as with "=" and "==" inside and outside an "if"
I tried to use C, but I spent more time defining what function was the "}" and looking for where the ";" I've never been able to make anything useful

[Aurel]

-

[edcronos]

Aurel

of course if you want to wait for some specific reasons
basically it's popcnt that Charles said he'd add.
even in blocks of 32 bit is already a great saving of processing.
nor do I know if in oxygen it has Bitwise Shift Function,
although I also have to learn how to correctly use the Array of oxygen


Charles Pegge

Did you speak in lisp,
particularly I think it can create mistakes in programming mixing so many possibilities, Oxygem would be the proper paradox,

basic and C for me does not have much difference off some details and symbologies, but Basic if a beginner look at the code can have an idea of what is being done, and in C still have to learn the symbologies.

, lisp is another story,
with their learning and being able to mix a language like Basic or C could be a lot easier to write really complex and very fast routines,
I think that there is logic that fits better in one language than in another

[Charles Pegge]

Here is a 32-bit popcnt emulation demo:

Code: [Select]

'mov eax,0xaaa
'popcnt ecx,eax
'print ecx '6
'
'popcnt emulation:
xor ecx,ecx
mov eax,0xaaa
mov esi,32
(
 dec esi
 jl exit
 shl eax
 jnc bitnotset
   inc ecx
 bitnotset:
 repeat
)
print ecx


The simplicity of LISP syntax is intriguing. We have 2 LISP interpreter experiments: projectsA/LeanLisp and projectsC/OxyScheme. But the distinctive and explicit structure of Basic makes it much easier to read, and we can use macros to accomplish similar flexibility without creating a forest of brackets.

[JRS]

My interest in LISP passed when Rob did.