On Thu, 16 Jul 1998, Peter Gerwinski wrote:
Procedure MyProcedure; asmname 'externalproc';
Perhaps 'ExternalProcName' would be more consistent here?
Possibly, but what I was trying to demonstrate was that the name of a procedure does not have to be the same name as the asmname declaration (I LOVE this features :)~~~ ).
Procedure MyProcedure( MyParam1 : @var{some type} ); asmname 'externalproc';
Giving the same name two times here might confuse ...
Hmmm... Should we just have one procedure declaration with parameters? Or should there be seperate declarations? Reason I have one of each (I know, I know, I didn't add one for the function :P) is to avoid the question of "Will asmname work on procedures with a parameter list?" Maybe there's a better way?
Hmm ... these are examples, not syntax descriptions, although I agree that they are more illustrative than a pure formal description of the syntax. Maybe we should take more use of the `@var{...}' macro ...
What does @var{} do anyway? :}
allows one to access variables, functions,
^^^(Is this correct and good English? Unsure - IANANS.)
I wrote it as "one" so that I can avoid saying "you", tho it might better to re-word it as "allows access to variables, function, ..." ?
Not true. That's what all of `external', `C', `C_language', and ... and `C_languages' which are indeed identical).
Noted :)
The commas and the point are essential in order to make `@ref{...}' work correctly.
Doh! :)
See ya! Orlando Llanes
"Meine Damen und Herren, Elvis hat soeben das Gebaeude verlassen!"
"Look out fo' flyeeng feet" O__/ a010111t@bc.seflin.org /|____. O <__. /> / \ ____________|_________ http://ourworld.compuserve.com/homepages/Monkey414