bug132

On Thu, May 03, 2007 at 07:22:35PM +0200, Markus Elfring wrote:
>Stefan Seefeld schrieb:
>>The easiest way to get involved is to download, run, and study the code,
>>then look at the issue tracker for inspiration, if you haven't run into
>>any bug or limitation yourself yet. :-)
>
>I reported the issue "Fix signal handler" 
>(http://synopsis.fresco.org/issues/bug132) as I've filed it for a few 
>other open source projects.
>
>But I do not want to fiddle with (low-level) source code before the open 
>design issues for AST, ASG, symbol table, overload resolution, template 
>processing and the like will be resolved.

I commented on bug #132, but since you seem to be anonymous and did not
even take it upon you to get yourself an account, you will not see any
comments, even short of the submitter being on the nosy list?

>                                          It seems that I can not 
>contribute C++ and Python coding at this stage. Let's look if this 
>situation can be changed ...

It's up to you now. I asked concise questions on why/what you think this
particluar thing is, from your POV, buggy to do and await your answer in
this respect in that very same issue report.

Note that i think that bypassing the atexit chain is not a bright idea
in this particular case.

Eagerly awaiting your hands-on suggestions; yours -- sincerely --

>
>Regards,
>Markus