Re: High Level Assemblers vs. High Level Language Compilers

kgw-news@stiscan.com
24 Mar 2002 00:17:57 -0500

          From comp.compilers

Related articles
High Level Assemblers vs. High Level Language Compilers whopkins@csd.uwm.edu (2002-03-19)
Re: High Level Assemblers vs. High Level Language Compilers rhyde@cs.ucr.edu (Randall Hyde) (2002-03-21)
Re: High Level Assemblers vs. High Level Language Compilers idbaxter@semdesigns.com (Ira D. Baxter) (2002-03-22)
Re: High Level Assemblers vs. High Level Language Compilers fjh@cs.mu.OZ.AU (2002-03-22)
Re: High Level Assemblers vs. High Level Language Compilers rhyde@cs.ucr.edu (Randall Hyde) (2002-03-24)
Re: High Level Assemblers vs. High Level Language Compilers rhyde@cs.ucr.edu (Randall Hyde) (2002-03-24)
Re: High Level Assemblers vs. High Level Language Compilers kgw-news@stiscan.com (2002-03-24)
Re: High Level Assemblers vs. High Level Language Compilers whopkins@alpha2.csd.uwm.edu (2002-03-31)
Re: High Level Assemblers vs. High Level Language Compilers rhyde@cs.ucr.edu (Randall Hyde) (2002-04-06)
Re: High Level Assemblers vs. High Level Language Compilers rhyde@cs.ucr.edu (Randall Hyde) (2002-04-06)
| List of all articles for this month |

From: kgw-news@stiscan.com
Newsgroups: comp.compilers
Date: 24 Mar 2002 00:17:57 -0500
Organization: Solution Technology
References: 02-03-120 02-03-127 02-03-154
Keywords: macros
Posted-Date: 24 Mar 2002 00:17:57 EST

On Sat, 23 Mar 2002 02:20:42 UTC, fjh@cs.mu.OZ.AU (Fergus Henderson) wrote: WEEKDAY


>"Randall Hyde" <rhyde@cs.ucr.edu> writes:
>
>>>> since C is really just a very very high level macro assembler.
>>
>>I totally agree with Alfred. C is a terrible macro assembler simply
>>because it's macro facilities are so weak. C (and derivatives) would
>>be a much better language if CPP were beefed up considerably (think
>>Dylan rather than GCC). However, the current trend is to avoid using
>>macros entirely in HLLs because of "semantic issues" (i.e., macros
>>don't behave like functions) that tend to confuse weaker programmers.
>
>I think part of the problem is that debugger support for C macros in
>most existing systems varies from weak to non-existent.
>
>A really good debugger would allow the "step" command to step through
>macro expansion.
You would get that if the compiler expanded macros with the
proper #line information although you wouldn't see
built symbols.


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.