Eros, my goal was to enhance the current code and create a complete replacement for it. If you can't make the source available, it wouldn't be possible to ensure backward compatibility.
I think...
Type: Posts; User: Robert Hodge; Keyword(s):
Eros, my goal was to enhance the current code and create a complete replacement for it. If you can't make the source available, it wouldn't be possible to ensure backward compatibility.
I think...
Thanks for your reply, Eros.
First, the current TB documentation file is in a slightly different order from the one you pointed me to. I thought the current TB release did not have an entry for...
Hello Eros,
The Linked List support in the data structure feature you refer to does nearly everything I might need. I have a few issues:
1. The feature doesn't appear in the current TB release....
The current Linked List module LL is clearly implemented as a singly-linked list.
I would like to see a doubly-linked list supported. The advantages would be ease of inserting and deleting nodes...
I believe the quote you cited is from the FAQ page of SPFLite as of version 6. We are now on version 7, which uses thinBasic as its script engine. There have been a few snags now and then, but...
Some of the ideas I have kicked around are from another language I have been trying to design, off and on, for a number of years.
As for the Basic-specific ideas, I am actually hopeful that Eros...
Yes, and that would be the deciding factor. Only the developer would really know if the same arguments would ever produce different results. Suppose the function were to fetch data from a read-only...
I think it's important not to get too carried away with the syntax. After all, the main idea is that you are trying to accomplish two things here. First, you are trying to save some typing, and you...
The trick would be in deciding how to 'refer' to the prior function results.
Let's take your example:
' example 1
If myFunc(1,2,3) < 0 Then
'...
ElseIf Function_RecallResult("myFunc") > 0...
My thoughts about "uniform" closures is that block ought to all be closed the same way.
In PL/1, everything ends with END, and C uses { and }. While "uniform" it doesn't really tell you very...
I am less sure about ELSIF and ELIF than I am about the other forms. But allowing for ELSEIF and ELSE IF seems like a good idea.
The ENDIF thing is understandable. It seems sort of odd that you...
When issuing debugging messages of one sort or another, it's often useful to have the line number where the message originated from. C programmers are familiar with a preprocessor name of __LINE__...
I am not sure who came up with the idea of using [ ] brackets as an array constructor, but I do like it.
If the notion of having a sorted array is useful enough, suppose the two ideas could be...
My goals for ORDER were less ambitious. There already exists an ARRAY SORT, so having ORDER apply to arrays is probably not necessary.
However, I think there was a recent idea about using [ ]...
After my initial post, it did occur to me that ORDER could/should be applicable to arrays, and that for strings, a case-insensitive version might be handly, and you noted. I am not quite sure how...
I have recently run into some peculiar responses to incorrect IF syntax. Basically you will get the IF without END IF message if you do "dumb" things like
IF IF condition THEN
statement
END...
It is common to use SWAP to put two items in ascending order, like this:
DIM ONE, TWO AS LONG
' ...
IF ONE > TWO THEN SWAP ONE, TWO
This type of code is so common, it would be convenient...
C programmers are familiar with its #line directive, which assigns a line number and optional (purported) file name to subsequent lines of code, so that error messages are based on the assumptions...
Your comment about putting an = sign in the function prototype gives me an idea.
Right now, a function can set a return value by assigning it to the keyword FUNCTION. Let's rewrite your...
Anyone who has used PL/1 is familiar with what they call "pseudo-functions", which in modern terms are what we would now call objects with assignment-operator semantics. PL/1 calls them...
If you ever take a course in what is called Theory of Computation, it turns out in most cases, it is impossible, or nearly impossible, to prove in all cases (a) that a program will terminate without...
A parser can get "broken" when the grammar itself is broken. The "grammar" is simply a set of rules, which are independent of any implementation. There is a parsing book that talks about conflicts,...
Charles, there were a couple of reasons for the "blank" operator (I think you mean blank concatenation operator, not just 'blank' - trying to be precise here).
First, it's very, very common to...
I have no wish to perpetuate further off-topic debates, so I will try to keep this reply as brief and polite as possible, under the circumstances. As it so happens, I DON'T watch TV news. That of...
I would ask that the off-topic issues please stop. It is uncomfortable and embarassing to read them. I started this with a serious idea - blank-delimited concatenation. Let's please keep this...