OpenEuphoria

I've used Euphoria for years.

I have a program called fileHunter that uses walk_dir in std\filesys.e. I use it regularly. I also use Eu 4 RC 1 with a legacy library. fileHunter compiles and runs well with this setup. I then installed Eu 4 RC 2. fileHunter compiled and ran, but gave totally wrong results. Thinking it might be the new library, I replaced it with the legacy library. Then it wouldn't even compile, claiming it couldn't find a clearly existing API entry. I was in the middle of a project and didn't have time to explore this problem further, so I dumped RC 2 and reloaded RC 1 from the backups and fileHunter compiled and ran beautifully. I am reporting this here instead of filing a bug report because RC 2, with no suitable upgrade path and too many errors, has become for me a dead issue.

A reasonable minimum upgrade path includes all of the old API, all of it working as before, plus additions for the new API and a text file identifying no-longer supported entry points as deprecated with suggestions for their replacement. I have about 30 programs written in Euphoria. Without a reasonable upgrade path, I cannot afford to upgrade.

I'll not be using in the future.