Structured Super Basic 2.7.2g

[Giorgio Garabello]

Original Post:
viewtopic.php?t=5227&start=20

Morning Derek.

https://github.com/SinclairQL/Structure ... tag/2.7.2g

2.7.2g is the latest. Details in the docs as to what changed. One thing I added that is incompatible with Tim's version,the line continuation character is "/" in Tim's but in mine it's "/+" as I often use PRINT statements with the trailing slash to get a linefeed. Those lines were combined with the next one and caused MISTakes.

Cheers,
Norm.

This is a problem. Backward compatibility is fundamental, for example this change prevents me from being able to use the latest version, I have been using SSB for years and I have hundreds of programs written with ssb!.

You could use double encoding...


Giorgio

[Derek_Stewart]

Hi,

As mentioned earlier, MicroEMACS can use SSB by Fileinfo, great I use all those.

I was hoping for a MicroEMACS macro to invoke SSB and process the file in MicroEMACS..

[Giorgio Garabello]

Hi,

As mentioned earlier, MicroEMACS can use SSB by Fileinfo, great I use all those.

I was hoping for a MicroEMACS macro to invoke SSB and process the file in MicroEMACS..

Of course, you can also do it through the MicroEmacs macro, we have several possibilities

Giorgio

[swensont]

Derek,

My latest version is here:
http://swensont.epizy.com/ssb272.zip

Norman has expanded it with some additional features.

The documentation for 2.7.2 details how to use SSB with MicroEmacs. That document is here:

http://swensont.epizy.com/SSB.pdf

See page 26 for a macro that calls SSBGO to execute SSB while still in MicroEmacs.

Tim

[NormanDunbar]

This is a problem. Backward compatibility is fundamental, ...

Check out the rest of the updates. Details of what I changed are in each version. 2.7.2f doesn't change the continuation character, for example.

https://github.com/SinclairQL/Structure ... c/releases

Cheers,
Norm.

[Giorgio Garabello]

This is a problem. Backward compatibility is fundamental, ...

Check out the rest of the updates. Details of what I changed are in each version. 2.7.2f doesn't change the continuation character, for example.

https://github.com/SinclairQL/Structure ... c/releases

Cheers,
Norm.

Yes I have seen the various changes, but I am thinking about how the future of this software will be...
Who wants to use the next versions will have to correct all the ssb sources that he had written? in my personal case, more than 100 sources
Who is the maintainer of the software? you or Tim?

Giorgio

[tofro]

This is a problem. Backward compatibility is fundamental, ...

Check out the rest of the updates. Details of what I changed are in each version. 2.7.2f doesn't change the continuation character, for example.

https://github.com/SinclairQL/Structure ... c/releases

Cheers,
Norm.

Yes I have seen the various changes, but I am thinking about how the future of this software will be...
Who wants to use the next versions will have to correct all the ssb sources that he had written? in my personal case, more than 100 sources
Who is the maintainer of the software? you or Tim?

Giorgio

I guess it shouldn't be too hard to write some Python or S*Basic utility that converts the line continuation characters?

[Giorgio Garabello]

I guess it shouldn't be too hard to write some Python or S*Basic utility that converts the line continuation characters?

Sure, but that's not the point.

[pjw]

I guess it shouldn't be too hard to write some Python or S*Basic utility that converts the line continuation characters?

Sure, but that's not the point.

It wasnt ideal to use a valid separator as a meta character in the first place, but thats water under the bridge.

The simplest might be to just change it in the SSB source code and compile your own version, Giorgio, and anyone else affected.

The maintainers should consider allowing both options in the next update.

Just my 2d's worth

[Giorgio Garabello]

I would add, other small considerations and personal notes.
1) Be able to download the . zip file in the same repository that you normally use, (i.e. either the Dylwyn site or Tim's, do not put it only on Github)
2) The . zip file cannot be unpacked on QL, (names too long)
3) the zip file does not contain the executable, only the sources and documentation, the software is optimized for Turbo so this forces you to install and learn to use this compiler.

just my two cents

Giorgio