XPL for Sigma 7 (GORDO)

kenr — Tue, 18 Mar 2025 03:08:59 -0000

I have an XPL XCOM compiler for the Sigma 7 / GORDO OS from 1968 -74 I'd like to get this this to run. I have your XPL C package and I intend to compile my XCOM with it to obtain Sigma code.

The first statement is DECLARE #.TERMINALS LITERALLY '44',
Which gives the error XPL to C language translator -- version 1.2
1 | DECLARE #.TERMINALS LITERALLY '44', |
|
*** Error, Illegal symbol pair: <identifier> <identifier> (detected at line 6448 in xcom). ***
Partial parse to this point is: <statement list=""> <identifier>
1 | DECLARE #.TERMINALS LITERALLY '44', |
|
*** Error, Illegal character: 2e (detected at line 1423 in xcom). ***
*** Last previous error was detected on line 1. ***</identifier></statement></identifier></identifier>

Is it true that ketwords like declare and literally must be lower case?
And, not surprisingly the dot character . cannot be used in an identifier?

Do you think I should modify the XPL C, or my several 1000 lines of all upper case code.

Thanks
Ken

Mentoring chats?

Brian Tiffin — Sat, 01 Aug 2020 04:00:40 -0000

:-)

When I get comfortable enough to make the XPL language page on Rosetta, your routine will be put to use for case conversion, not the first day student copy listed above.

I was about to pester about learning the ins and outs of references vs copies. REBOL programming seems a little similar in that area. When to leverage the efficiencies of references and when new copies need to be made. Thanks for the hint.

Getting over the first few hurldes, will add base handling to the sum-digits task sample. Secondary goal after that baby step will be trying to get the same XPL sources compiled and running on MVS 3.8j and with your XPL to C compiler.

Have good. make well,
Blue

Mentoring chats?

Daniel Weaver — Sat, 01 Aug 2020 00:38:36 -0000

The line:
total = total + digit - byte('0');
Should read:
total = total * base + digit - byte('0');

This should work for any base from 2 to 10.

In my example the function UNIQUE makes a copy of the string so that the uppercase function does not corrupt other strings.
For Example:
stuff = 'abcdef';
new_stuff = uppercase(substr(stuff, 1, 3));
/ Should not corrupt the value of the string "stuff "/

It's easy to get a unique copy of a string. You move it to the top of the free string area.
Example:
new_string = substr('?' || old_string, 1);

Mentoring chats?

Brian Tiffin — Fri, 31 Jul 2020 12:35:31 -0000

Thanks again.

I spent about a year back in the early 80's under a mentor who was the "structured programming, or no programming" type. Thinking back, he may have been from Denmark and loyal to the likes of Dijkstra. <joking></joking> It was good training in goto-less at all costs programming. :-)

I'll post more starter questions if/when I put up the Rosetta Code XPL page and some of the simple tasks.

Cheers,
Blue

Mentoring chats?

Brian Tiffin — Fri, 31 Jul 2020 11:22:48 -0000

Nice. Thanks, Daniel.

Works the charm.

Did have to fix the /* */ comments in the first line. SourceForge markup ate the asterisks for italics. Not a biggy, and on par for SourceForge markdown expectations. :-)

Have good, make well,
Blue

Mentoring chats?

Daniel Weaver — Thu, 30 Jul 2020 10:50:57 -0000

The lack of a BREAK statement in XPL is a problem. There are a few ways to work around this problem. Here are some suggestions:

looping = 1;
do while looping;
if some_end_condition then looping = 0;
/ do more stuff /
end;

/ In XPL the upper limit is not recalculated /
/ This will not work /
x = 100;
do i = 0 to x;
if some_end_condition then x = 0;
/ ... /
end;

/ But you can change the index variable /
x = 100;
do i = 0 to x;
if some_end_condition then i = 256;
/ ... /
end;

/ You can also use the goto statement /
do i = 0 to 100;
if some_end_condition then goto exit_label;
/ ... /
end;
exit_lebel: / Loop escape /

/ At times I will put the loop into a seperate procedure /
search:
procedure;
do i = 0 to 100;
if some_end_condition then return;
end;
end search;

Dan

Mentoring chats?

Daniel Weaver — Thu, 30 Jul 2020 10:34:32 -0000

/ lower to UPPER case conversion /

declare map(255) bit(8);

declare shift character initial (
'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ');

initialization:
procedure;
declare (i, j) fixed;

  do i = 0 to 255;
     map(i) = i;
  end;
  do i = 0 to 25; 
     j = byte(shift, i + 26);
     map(byte(shift, i)) = j;
  end;

end initialization;

uppercase:
procedure(s) character;
declare s character,
i fixed;

  s = unique(s);
  do i = 0 to length(s) - 1;
     byte(s, i) = map(byte(s, i));
  end;
  return s;

end uppercase;

main:
procedure;
output = 'abc...xyz->' || uppercase('abc...xyz');
end main;

call initialization;
call main;

eof;

Mentoring chats?

Brian Tiffin — Sun, 05 Jul 2020 00:26:25 -0000

Not meaning to pester, Daniel, but also keen and at the bottom of the XPL learning curve.

Are you up for a few beginner questions here in your discussion forum?

As a for instance, how would an XPL guru go about defining uppercase(str) and lowercase(str) procedures, given that the code should be EBCDIC and ASCII agnostic, changing the str in place.

I've tried a few things like byte(str, pos) = byte(map, j) on the left hand side of an assignment, but all I seem to get, is more confused. :-)

Another; in the conversion section, CHARACTER -> Integer is illegal. How about a simple convert of '1' to 1? More to the point, not using compile time literal syntax, but from substr or indexing.

n = substr('1234', 1, 1);

Don't want the character code for '2', value, but a numeric 2, computed at runtime. Again, ASCII EBCDIC agnostic if possible. More than willing to scan tables of suitable digits depending on base.

If you don't feel like being a first level XPL student tech support question answerer here, Daniel, then that'll be ok. ;-)

Plan is to fill out some Rosetta Code entries for XPL, and I like to start with some Simple Tasks to get over the new to XPL hump. Things like the Sum digits of an integer (in a given base) task. I'd like the solution to cover more than just the bit-string default types and conversions built into XPL. From 2 to say base-36.

Oh, and just in case you don't mind the simple minded starter questions. One last one (for now). Is there an idiom for terminating a counted loop early? For example, looking to see if a character is in a map, leave when found, in a do loop counting across the length of the map. Is it simply what I think it is, a DO WHILE with & and | logical operators in the expression and explicit counting in the loop?

Again, an answer of 'go read...' will be ok, Daniel. This is all currently for fun. If things work out, the goal will be a demo of an XPL to C generated DSL, embedded in COBOL. For now, simply for the joy of the pursuit.

Have good, make well,
Blue

XPL documentation

Daniel Weaver — Fri, 01 Dec 2017 20:51:07 -0000

Here is a link to the XPL documentation for the original XPL compiler.

http://teampli.net/XPL/ldindex.html

Suggestion for extension to simplify access to POSIX functions

Douglas Wells — Mon, 27 Nov 2017 23:40:50 -0000

I enjoy investigating new/old languages, and have adopted a set of
successively more difficult commands to develop in such a languages.
This includes hello-world, a POSIX-like echo, a POSIX_like cat, etc.
I'm up to the point of writing a network program to fetch the time
from a remote system. That now works, but the compilation process is
annoying.

Since your XPL package doesn't include such network functions, my
method is to use forward declarations, but never to actually define them
as XPL procedures. Because your XPL compiler translates to C, this
allows me to get at the system functions. For example,
declare socket label;
...
fd = socket ( ...);

The problem is that the compiler (reasonably) complains above the lack
of such a definition, using several screen lines to complain. This
obscures any "real" problems that the compiler might have diagnosed.
The "-W" compiler option is close, but I really do want to see
warnings about undeclared variables.

Do you have any suggestions about a better method? What do you use?

Perhaps you might consider an XPL extension of something like:
<type> ::= label external
<type> ::= label external <string constant="">
where the "external" would signal the compiler that the procedure was
external, and the <string constant" would specify the external name of
the procedure to be invoked (Ada, Fortran, FreePascal ... all behave
something like this).

And again, thanks for releasing your XPL compiler.

Recent posts to Discussion

XPL for Sigma 7 (GORDO)

Mentoring chats?

Mentoring chats?

Mentoring chats?

Mentoring chats?

Mentoring chats?

Mentoring chats?

Mentoring chats?

XPL documentation

Suggestion for extension to simplify access to POSIX functions