From mint-bounce@lists.fishpool.fi Fri May 29 01:41:53 2009 Date: Fri, 29 May 2009 07:33:37 +0200 (CEST) From: Frank Naumann X-X-Sender: fnaumann@localhost.localdomain To: =?ISO-8859-15?Q?Vincent_Rivi=E8re?= Cc: mint Subject: Re: [MiNT] New include/mint/sysbind.h In-Reply-To: <4A1E53EE.8040904@freesbee.fr> Message-ID: References: <4A1E53EE.8040904@freesbee.fr> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=- tagged_above=-50.5 required=7.0 WHITELISTED X-Spam-Level: X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: fnaumann@boerde.de Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Hello! > About the monolithic sysbind.h, it annoys me that if I want to write pure TOS > software, I include only , then I will get the MiNT system calls, > too. So I could use dependencies to MiNT without knowing it. Same thing about > Metados, etc. I think the Metados and Falcon syscalls can be detected easily by name. Beside from that I don't think you can clearly separate the namespace between TOS and FreeMiNT. What about MagiC? Finally you end up including mintbind.h too. Regards, Frank -- ATARI FALCON 060 // MILAN 060 ----------------------------- http://sparemint.org/ e-Mail: fnaumann@boerde.de