Re: Bug in std/base64.e
- Posted by ghaberek (admin) 3 weeks ago
- 1576 views
I'm trying to test this out in a dev container in VSCode.
Full disclosure: I have not touched the vscode-euphoria extension in a while so I'm not sure what state it's in.
As I recall, any further improvements required writing a language server which hasn't been high on my priority list.
I put my code changes in, and modified my tests, but when I run eutest tests/t_base64.e, it doesn't seem to be picking up my code changes. I even tried putting in a deliberate bad statement to see if I'd at least get some type of error, but I'm not seeing any error. Is there something I need to do to force the code to recompile or to clear some cache?
Never mind. I have to run the tests with -i $(pwd)/include.
Yep. By default your interpreter is going to be using the include files it's pointing to in eu.cfg where it's installed.
So if your interpreter is /usr/local/euphoria/bin/eui there should be eu.cfg that contains -i /usr/local/euphoria/include
When you build Euphoria, the configure script creates a new eu.cfg in the build directory that points to the include directory next to source.
So if you're building in /home/rzuckerm/euphoria/source/build, that eu.cfg should contain -i /home/rzuckerm/euphoria/include
I also need to mention that I am using WSL2 with a Ubuntu 22.04 installed. I am using Windows 11.
Excellent! So am I. Actually it looks like I'm on Ubuntu 24.04. But I've been using WSL as my primary development environment for a while now. At least since WSL2 came out in 2019.
Pull request is ready for review: https://github.com/OpenEuphoria/euphoria/pull/16
All of the checks passed, so that's good. Although currently that just means the builds completed. I don't have the actions running unit tests because many of the tests need correcting to pass. Yet another thing that needs some attention around here.
I have merged your PR. Thanks!
-Greg
