OpenEuphoria

Re: Threads

• Posted by "Juergen Luethje" <j.lue at gmx.de> Apr 24, 2005
• 524 views

codepilot Gmail Account wrote:

> One time I wanted to make a web server, so I looked at some other
> ones, and some tutorials. I saw several ways to use winsock. I started
> with the blocking methods just because they seemed easiest. Then after
> only one connection at a time was possible, I started to think. At the
> time I was taking a C++ class at school so most the tutorials I looked
> at where C. I had been using euphoria for years by then, and wanted to
> do a euphoria web server. So I started to port a threaded web server
> tutorial to euphoria. And the threads did work, for a minute. Anytime
> I printed to the screen, it crashed, and randomly all the time. Then I
> read somewhere that euphoria wasn't thread-safe, and I was
> heart-broken. The language that was my favorite, and had used for
> years, and wrote lots of stuff in was not able to do something that I
> really wanted to do.
>
> So I gave up and wrote it in C. Then later I came back to it, and
> found the asyncselect command in winsock, and made it with win32lib in
> euphoria, and was kinda disappointed at the speed, but happy it was
> possible.
>
> So while everything may be possible in euphoria without threads, it
> kinda hurts that there not there when you want them. It hurts speed,
> algorithm choices, and even the user base, which I think would be
> bigger otherwise.

I think that's an important point. Porting code from "classic"
procedural languages such as C, Basic or Pascal shouldn't be too hard,
especially since many algorthms are already implemented in these
languages, and not in Euphoria. These considerations not only apply to
threads, but also to other things, for instance the 'continue' statement.

<big snip>

Regards,
   Juergen