Lpc2000

Jaya,

I've already provided an example of where it can cause problems:

If you have an application that makes extensive use of processing on 
128-bit numbers using in-line assembler (as someone suggested) , what 
happens when you want to port that application to another 
environment? Bit of a problem, I think.

All I suggested for this case was to implement a few core functions 
in assembler in a separate compilation unit (i.e. file) and re-code 
that for the new environment. No need to touch the application itself.

Jaya, I'm well aware that others take a different view and have 
different experiences to draw on and will come to different 
conclusions about how to use particular features. All I'm and others 
are doing is pointing out some potential pitfalls. 

There's no need to be abusive about it!

Brendan

P.S. you might want to correct some of the factual errors in your own 
writings on your Web site, before attacking others so aggressively.

--- In lpc2000@yahoogroups.com, "jayasooriah" <jayasooriah@...> wrote:
>
> --- In lpc2000@yahoogroups.com, "brendanmurphy37" <brendan.murphy@>
> wrote:
> 
> > I think your suggestion is misplaced: why would you think that 
> > anyone pointing out the pitfalls of a particular feature doesn't 
> > understand it?
> 
> Your interpretation is misplaced.
> 
> I asked Robert for an example of inline assembler that "causes more
> problems than it fixes".
> 
> If you have one, put it up for discussion.  If not, I have nothing
> more to say to you.
> 
> Jaya
>