From:	hansoft AT visitweb DOT com (Hans 'the Beez' Bezemer)
Newsgroups:	comp.os.msdos.djgpp,comp.lang.c
Subject:	Re: Scripting language library
Date:	Tue, 16 Dec 1997 06:39:45 GMT
Organization:	HanSoft & Partners
Lines:	24
Message-ID:	<34962190.1704432@news.xs4all.nl>
References:	<348e5375 DOT 789931 AT news DOT xs4all DOT nl> <3494eaf4 DOT 492512 AT news DOT xs4all DOT nl> <67453a$t1v$1 AT home DOT edu DOT stockholm DOT se> <3495ac96 DOT 1274644 AT news DOT xs4all DOT nl> <6751v0$t6d$1 AT brie DOT direct DOT ca>
Reply-To:	hansoft AT visitweb DOT com
NNTP-Posting-Host:	ztm01-28.dial.xs4all.nl
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

bill AT cafe DOT net (Kaz Kylheku) wrote:

>Defining  begin to stand for { and end to stand for } buys you absolutely nothing.
Don't agree, but I won't repeat all arguments again. From a focal point of
view, { } are easily "mistaken" for ().

>All you are doing is polluting the macro namespace. If some header file uses 'begin'
>or 'end' for any purpose, it will break. Macros should not be used frivolously.
>If you must define macros in some module's header file, they should be prefixed 
>in such a way that they are identified with the module. An identifier such as 'end'
>is a poor naming choice for a globally used macro.
>	#include "pascal.h"
It has it's own header file, called easyc.h

>	static char *fill(char *beg, char *end);	/* oops */
After tens of compilers and platforms I've never encountered the problem.
"token", yes. "begin", never.

Hans
================
"First make it work, then improve it."
Visit our website! http://visitweb.com/hansoft

*** Home of the 4tH compiler! ***

- Raw text -