Shawn and Backend inclusion
- Posted by jimcbrown (admin) May 22, 2015
- 1437 views
Forked from Re: Wee: standard installation
Being willing to include Wee but not the include file it needs seems a bit weird.
It isn't going to matter. As long as you keep it available for those who need it, what is the benefit to including this with the distribution? If the admins agreed with me, sockets, regex, and http would not be included in the core c files. The minute you include it with the interpreter, they will talk about adding it to the backend. I know them. ;)
Shawn Pringle
This is so wrong that it's hard to know where to start.
I'll start with http. That's still written in Euphoria, it's not in the C backend.
Regex could go out of the backend. We've talked about it before, but it's extra work with little visible end user benefit. The reason for regex to be done in the backend was for DOS (where we couldn't load it as a so or something), and is no longer valid.
sockets went into the backend because it was easier to do it in C than using pure Eu to wrap the libc/stdlib calls. A lot of C macros for BSD sockets that were hard to wrap for example, especially across Unix platforms (where each macro had a slightly different value on a different OS - bleh). I suppose it could have been done as a C so shim though (where the hard to wrap macros are wrapped in easy-to-wrap C function calls, and then the .so file is wrapped in an Euphoria include file).
