Format of output results

[rzuckerm]

I'm going to be implementing a prime solution in ALGOL 60, which has very limited output formatting capability. The outinteger and outreal functions output the value followed by a space. Therefore, the result would look like this for any computed value:

<label>;<iterations> ;<total_time> ;1;<tags>

Is this going to be a problem?

[davepl]

Could your benchmark script pipe it through sed or similar and transform it as needed? Your binary might be limited, but perhaps the runner can compensate? Not sure, just thinking out loud :-) - Dave

…

On Mar 21, 2026, at 11:40 AM, rzuckerm ***@***.***> wrote: I'm going to be implementing a prime solution in ALGOL 60, which has very limited output formatting capability. The outinteger and outreal functions output the value followed by a space. Therefore, the result would look like this for any computed value: <label>;<iterations> ;<total_time> ;1;<tags> Is this going to be a problem? — Reply to this email directly, view it on GitHub <#1049?email_source=notifications&email_token=AA4HCFYEZYYXDJDOZ2O3J5T4R3O3DA5CNFSNUABAM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPHE3TCNJYGE32M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4HCFY4FFF7ZDR7EKAHIKL4R3O3DAVCNFSM6AAAAACW2GGH46VHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZZG4YTKOBRG4>. You are receiving this because you are subscribed to this thread.

[rbergen]

I was typing exactly that, haha.

Yes, the benchmark runner will choke on the spaces, but piping it through one of the standard shell tools will easily fix that. I'm also happy to help with that, if needed.

[rbergen]

@rzuckerm This should do the trick:

algol_sieve | sed 's/ *;/;/g'

Again, I'm happy to help apply this to (a Docker-executed) Algol 60 sieve runner, once available.

[rzuckerm]

Thanks @rbergen . I have it figured out. Will have a PR soon.