[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Gcl-devel] Re: [Gcl-commits] gcl h/protoize.h h/usig.h o/file.d o/

From: Mike Thomas
Subject: RE: [Gcl-devel] Re: [Gcl-commits] gcl h/protoize.h h/usig.h o/file.d o/makefile o...
Date: Wed, 15 Jan 2003 13:42:04 +1000

Hi Camm.

| The 1 vs. 3 argument signal handler is toggled by the SA_SIGINFO flag
| passed to sigaction, which I think is set on nearly all architectures
| now.  It is used, for example, to pass fault addresses to the sgbc
| code on machines where this works.  I take it this is designed to
| remove a compiler warning.  If memory serves, gcc cannot yet ( and I
| don't see how it ever could) distinguish between the two handler forms
| depending on sigactions' arguments.  So I typically make an explicit
| cast in this case, (from linux.h:)
| action.sa_handler = (void *)memprotect_handler; \

I'll read further on this when I have some time.

| It would be nice as we go along to
| minimize the MINGW ifdefs in the core code, and move this to the .h
| files or to configure-generated gclincl.h where possible.

I agree about minimising the number of platform specific ifdefs where

| As always, I defer to your judgment.


Mike Thomas.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]