I’ve been very busy testing the revision 16 of xblite version 2.41. I went in places where no Xbliter’s feet touched ground, and found corner cases that only a gorilla could cause. And I am so sure that I covered all the potential mishaps that I dare you to break the xblite.x that I post here! Because I am moving on to Release 17, which is supposed to be XBLite support for native Windows Unicode.
But, allow to brag a little bit about this release 16: I truly believe that the new directives CODE, GRAB and STRIP are great additions to an already rich language, in the sense that they open huge possibilities in 3 directions:
- CODE for assembly injections,
- GRAB for code re-use,
- STRIP for obesity control (of your XBLite programs, not your bodies…)
I first intended to propose a crude pre-processor: CODE, GRAB and STRIP were at first source directives and their output are saved in separate XBLite source files for whatever you would to do with them. However, I decided to treat CODE as a normal XBLite operator: I succeeded to break badly the CODE directive while injecting really huge pieces of GoAsm code. Since I had a previous implementation of CODE as a normal XBLite key word, I tried the old CODE version and it worked nicely! Well, you can beat success! CODE is and will remain an XBLite operator, unlike GRAB and STRIP, which remain pre-compile directives and yield to a new (and improved) source file.
I remember an Xbliter proposing to handle Xblite GUI with a set of new operators; I believe that GRAB can handle this project.
I we come up with a satisfactory solution, I can expand XBLite’s syntax and code generation to generate working GUI applications, for GTK...
I would welcome a self-explanatory syntax such as:
DRAW mainWindow LAYOUT "example .xml" ' example.xml would be a subset of an HTML form
POST mainWindow AT (10, 5)
OK! Release 16 is a good to go for me, unless you prove me otherwise.
I am starting to work on the design of a clean distribution.
We have David Szafranski’s XBLite Forum, but as far as I know, only registered Xbliters can download files from the Forum. All that are interested for a distribution thru the Forum should try to download a file and let me know if they succeed.
I can also distribute XBLite compiler and libraries thru SourceForge, which host 2 of my (XBLite) projects. However, I would rather carry on the way David would have done.
Happy xbliting, and post here you grain of salt.
Hi D.! Hi
Here is my final of xblite.x Revision 16.
Nothing new, except:
1.Commented and restructured the new code for peer review (yours, obviously).
2.Rewrote the STRIP algorithm, and succeeded to cut its execution time in half.
On my pet program vxbl.x:
to strip off a single FUNCTION, from 47,580 lines to 47,560 lines,
duration was 43,578 milliseconds, and is now 19,437 milliseconds.
Congrats on the continued development of xblite! I concur with Alan on the two points mentioned above. Regarding the prolog code error, that bug was mine. I struggled when I wrote it whether I had it right or not, guess I missed it.