It would be nice to have examples of message-passing code,
using the three different ways of passing messages: to a single
thread, to a class of subscribed threads, and to all threads.
I think that's what you're saying.

Maybe some day I will provide such examples on the website. The
test programs that I use for development aren't really good to use
as examples because they're not stable. I keep changing them to
test various kinds of things.

However before I worry about having more examples I want to post
the one I have (see the attachment from my last note). That means
I have to write some more HTML, rebuild the zip archive, and so
forth. None of that is hard but it takes time.

If any of you has any code using Cheap Threads that you have posted
on your website, or elsewhere, I'd love to link to it.

Scott McKellar mck9@...
http://home.swbell.net/mck9/ct/

gordonwkf wrote:
>
> May be lessions of 1(thread) to 1(thread), 1 to many, manay to manay?
> Anyway, when I get time to read over your source code, I will
> provide some example for it, I may try to port your CheatThread to
> Gameboy Advance, since I am developing a Simple OS for GBA to drive
> my GUI interface.
>
> --- In cheapthreads@yahoogroups.com, Scott McKellar <mck9@s...>
> wrote:
> > See response below...
> >
> > gordonwkf wrote:
> > >
> > > Dear Sir
> > > Can you write more doc for funciton prototypes' parameters?
> Which
> > > make it more easy to use? Are there any more examples?
> > >
> > > Gordon From Hong Kong
> > > thx
> >
> > I tried to provide detailed documentation, but there's always
> > room for improvement.
> >
> > Which parameters are you having problems with?
> >
> > As for examples...
> >
> > One weakness of the website, as it stands now, is that it has only
> > one example -- the cttimer program, which may be too simple to be
> > very helpful.
> >
> > I'm not sure how to provide good examples. In order to demonstrate
> > anything beyond the simplest concepts, a program may have to be
> > complicated enough that it's hard to follow.

<snip>

> > Another problem is that it's hard to show that multiple threads are
> > running without some kind of graphical display.

<snip>