<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY id=role_body style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: Arial"
bottomMargin=7 leftMargin=7 topMargin=7 rightMargin=7><FONT id=role_document
face=Arial color=#000000 size=2>
<DIV>
<DIV><FONT style="BACKGROUND-COLOR: transparent" face=Arial color=#000000
size=2><BR>> Michael Van Canneyt wrote:<BR><BR>>Well, if we're going in
that direction anyway: <BR>>Why not include all possible assembler
instructions then ?<BR>><BR>>Let's be serious. You must draw the line
somewhere.<BR>>I think these instructions are so exotic, they are pollution
of the system unit.<BR></FONT></DIV></DIV>
<DIV></DIV>
<DIV> </DIV>
<DIV>I agree with Michael. And I think the line is clearly drawn. The FPC
(and more importantly the language syntax itself) design goal, as I
understand it, is to be, as much as possible, platform and architecture
independent and doesn't need to be "polluted" by adding esoteric
functions/(worst yet)operators becuase they are neat on one particular type of
machine and we just program around them everywhere else.</DIV>
<DIV>Rather, if your application really needs that function, you have
a number of suggestions on how to implement that within your own
application, so do that, but I don't think the compiler should be expected to do
it for you. </DIV>
<DIV> </DIV>
<DIV>Dave</DIV></FONT></BODY></HTML>