Re: Someone changed my Thread Manager writeup?
Hi Al
I think your "Thread Manager" fills an important need and would like
to thank you for developing it and then making it available to
everyone.
There are times when "simplicity" of algorithm provides speed which
enables it to match (or even out perform) more complicated predictive
algorithms in certain tasks (not necessarily all tasks). As far as
the end user is concerned, it "looks" and "performs" like its more
complicated "relative". In some cases it may even seem to the end
user to be "better".
In other words, it's about results from the end user (user of the
created software) perspective rather than method.
I find Euphoria itself to have this "quality" - an elegant
simplicity.
I would ask you not to increase the library's complication in order
to perform tasks more like a "real" thread if there is no obvious
benefit to the end user for those certain tasks it is good at.
Naturally no one tool is right for all purposes. But we now have a
tool we did not have before. Thanks.
You asked about a new name for the library. Perhaps "Software Pseudo
Threads" ?
--
David
On 10 Aug 2005 at 11:30, Al Getz wrote:
>
>
> posted by: Al Getz <Xaxo at aol.com>
>
> Ferlin Scarborough wrote:
> >
> > Ferlin Scarborough wrote:
> > >
> > > Therefore, would it not be called something like Simulteanous
> > > Events Manager?
> > >
> >
> > Sorry about that it should be Simultaneous Events Manager.
> >
> > Later.
> >
> > Ferlin Scarborough
> >
>
> Hi Ferlin,
>
>
> Well, i wanted to call it something that was already familiar to
> users and not make them wonder what the heck it was :)
>
> Right now im thinking about "Thread Manager for Pseudo Threads",
> because it is in fact a threading manager, but the threads arent
> 'true' threads the way i think most people would expect (at least
not
> yet). Funny thing is, in thinking about a second version (that
allows
> true time slicing with the usual thread polling) im comming up with
a
> more complicated model that, to the end user, will appear exactly
the
> same for many gui applications! Yes, it will be closer to 'true'
> threading, but the only one who will know the difference will be
the
> person that programs the app! That's another reason why i have to
> call it some sort of threading or another, even before version #2.
>
> At least it performs a function that is useful to applications
> even the way it is now, so what the heck :)
>
>
> Take care,
> Al
>
> And, good luck with your Euphoria programming!
>
> My bumper sticker: "I brake for LED's"
>
>
>
>
|
Not Categorized, Please Help
|
|
