OS4.1 bugs

@xenic

ARexx can't be "fixed", it's old 68K code that doesn't belong to us and we're not permitted to change it.

@tonyw

I just noticed this night that it's possible to add multiple *public* semaphores with the same name, given the name is used as a key it sounds strange for me. Is it a bug or a feature ? If it's a feature how one is supposed to choose which semaphore is the one he wants ?
Also it's worth mentioning in the autodocs what happens when the semaphore is freed with FreeSysObject and it was in locked state (what about when it's collected in case of crash and ASO_NoTrack was false) ?

@tonyw

I?m probably putting a stick in a hornet?s nest now, but...are you allowed to tell if there is some kind of "exchange" planned for the "not fixable" AREXX?

Very interested here, because using AREXX scripts for a lot of things

Thanks a lot

Hi @Raziel
#223
Very interested here, because using AREXX scripts for a lot of things
I thought the OS4 system was going to update to use Python. Name one thing ? Maybe there is a Python script to handle it.

@Snuffy

My own script to minimize the hassle with ctorrent

It's a nice script

@Raziel
Years ago I tried the 68k Regina Arexx interpreter on my A4000 and it worked fine. However, I still needed the standard ARexx libraries to be installed because Rexxmast won't work without them. I did disassemble the Rexxmast program with the "Resource" disassembler but the code is over optimized for size and difficult to understand. I would say that a really good 68k assembly programmer could duplicate the functionality of RexxMast in C language but it would be really difficult. I don't think it would be that as difficult to port the Regina ARexx interpreter but I doubt if its going to happen any time soon.

@xenic

Some years ago I also looked at a rewrite of the RexxMast code. It's been written for speed and memory size, and uses lots of 68K tricks that you would have to abandon in a pure "C" version. However, without the author's permission to rewrite or modify it, any work is a waste of time. It also has so many bugs that would be difficult to duplicate in a "C" version, that it would be incompatible with the original.

@Raziel

I think we would all prefer ARexx to fade away into the sunset and be replaced by Python. AFAIK the OS4.1 Installer is written in Python (but no first-hand knowledge).

@tonyw

Quote:

Trouble is the current python arexx.so module does not set or extract the equivalent of ARexx's RESULT variable, so is very limited when interacting with programs arexx ports.