Re: What is the status of Euphoria V4.10?
- Posted by ghaberek (admin) Feb 02, 2019
- 2969 views
First, fix all errors indicated by the failing unit tests!
AGREED! A lot of the tests seem broken, so they're false failures.
In particular with respect to std/net/http.e:
- Adapt the std/net/http.e routines to use the CURL library so that the other http tests actually pass. See https://github.com/shawnpringle/euphoria/tree/http-curl for an implementation of this.
- Fix the [[OpenEuphoria.org]] web server to provide the resources that the above tests rely on.
- The curl branch needs documentation that EUPHORIA requires CURL, curl needs to be a requirement in the install and deb file creation.
You're using WinInet on Windows, correct? We should assume that library is always available since it was added in Windows 2000.
When using CURL on Linux (or OS X) I recommend we fall back to the existing routines if we can't find CURL, and issue a warning like "CURL not found. HTTPS will not be available."
Also, since the existing HTTP routines support tasking, let's make sure to include task_yield() in the WinInet/CURL call backs, assuming it's safe to do so.
Unit tests that deal with literal numbers that are too small to be put into a Euphoria atom, and should report an error rather than being read as zero or worse a huge number, are failing on my machine and probably most machines because these limits are different depending on the processor capabilities. The path of least resistance is to create an alternative set of control files for machines that have this capability and possibly adapt the testing program to use those.
I'm not sure I follow. Can you provide an example?
-Greg
