|
The pun was unintentional. Our approaches are similar in regard to the goal of simplification pushed to the limit but XyBasic works by translating the simple into the standard, baroque XPL; you make your simple source work directly on your engine. My language was a front end for XyWrite; yours is a front end for . . . Python? AutoIt? Are you going to translate the whole U2 file into the new syntax? Probably a breeze for Claude to do. What you're doing is very exciting. Opens the gates. Onward and upward, Harry On Mon, 22 Jun 2026 17:52:21 -0400, Carl Distefano wrote: > Reply to note from harrybinswanger <dmarc-noreply@xxxxxxxxxxxxx> Mon, 22 Jun 2026 12:06:39 -0400 > > Harry, > > > You did basically what I did. > > Ha, pun intended? ... What I did -- am doing -- is summed up in "It's all XPL": a unified syntax that works on the command line, in the KBD file, and in scripts. The distinction between commands and functions is abolished -- everything is a command (or "verb"). Commands are chained together with semicolons; in scripts, semicolons and newlines are 99% interchangeable. <VA$nn> variables are now just plain-text `$nn`, and they're accessible directly without first being assigned to a "save/get" or user variable. So if you're editing an XPL script and want to run it, `RUN $FP` on the CMline does it. KBD-file usage is cast in the same mold and much simpler than in XyWrite (the commas are gone): > > ; single character > nn=A > > ; multiple characters a/k/a strings > nn="My name is \"Ada\", what's yours?" > > ; single command > nn=AB > > ; multiple commands > nn=SA;AB > > ; Delete DeFine else single character > nn=IF $DF;DZ;RD;ELSE;RC;EI > > It's coming along nicely. Yesterday I added Auto-Replace. > > -- > Carl Distefano > cld@xxxxxxxxxx > |