Re: OpenEuphoria's Strategy
- Posted by katsmeow Feb 07, 2015
- 2295 views
euphoria style guidelines, adding doc comments, a few redundant functions from the stdlib removed, a few include statement changes, finishing the split out of the demo client from irc.e and some test routines are all that the code needs. it's only a few dozen lines.
Ne1uno, respectfully and pleadingly, if you intend to alter the irc.e code i submitted, i want to see and run tests on the code after you alter it. I duplicated a little code from the std libs because of path issues mostly. Some devs hacked code i submitted before, and could not get it to work, and at least one did/n't hack an unknown version i do not recall giving him and he couldn't get it to work. I also want to see if you changed it so much that my irc6.e and irc_client6.exw is still valid or i should quit working on them. I have a cute trick i want to try, but not if it isn't going to be considered, or if you will be editing it out anyhow.
Regarding the taskmsgs.e , using that with news.e and http.e makes them multitask much better than without. I was hoping to get http.e to taskmsg the entire webpage it was retrieving, but there was something fishy about a function call needing to complete anyways, or something. However, that's when run interpreted. If they don't run tasks when compiled, ummm, then stop working on the compiler, please. But otherwise, due to interactions with the devs, i gave up so hard and definately, i don't remember (and didn't bother to look) which was the last best version completed. I remember i deleted some code, i think i deleted the entire directory, and all that wasn't deleted was in the news.e dir, and a single copy of what was on my website.
Kat
