Re: Ada Library, called, returns and continues ?

[Patrick <patrick@spellingbeewinnars.org>]

Hi Dmitry

"100K lines of GUI code or 100K lines altogether? "

The whole toolkit. I can understand this with difficulty. I was thinking about reworking FLTK. I wanted to write a C wrapper around it's C++ core and then bind to this. I was thinking the widgets could then be rewritten in Ada. I still might do this but my family demands have intensified again. I haven't programmed in a month and I looking for something easier.

I was thinking that if I could bind an Ada entry to C, I could use a gui toolkits idle callback to retrieve information that could be processed in the back ground such as data being collected from an instrument, a bitmap image being generated from svg etc..

If a protected object and it's entries are bound to a C/C++ application with it's own main, do you think the Ada threads will begin when the C main is called or would I need to create an initialization for them? If they just started, main C could call an entry or If I used a protected record I could also access this as a struct and retrieve data this way. Do you think I could send data back and forth through the protected record?


'You also need support for unsolicited calls from Ada tasks. Consider a
progress bar indicator driven by an Ada task. At some point it should send
a message to the main thread to update the bar state. The main thread has
no idea about when and if that could happen. "

yes, I don't know how to do this but perhaps I can do this in a year or so when I am further along.

> I know eval is evil but if used
> sparingly I think it could be quite powerful

"No, it is not."

Okay, I stay away from it.

Thanks again for your feedback.