[m-dev.] for review: removing --args simple

Zoltan Somogyi zs at cs.mu.OZ.AU
Mon May 31 16:58:41 AEST 1999

> It's true that with this change we are only using one argument passing
> convention, but that may well change in the future, with high-level C,
> bytecode, etc.  Many compilers for other languages, e.g. GNU C, MSVC,
> support multiple calling conventions, with ways for the user to declare
> that a particular function has a given calling convention.  This is
> useful in cases where the function is imported, exported, or has its
> address taken.  I think that the likelihood that we will need an args_method
> or calling_convention field in proc_infos is quite high.

However, if we do, the current method of setting it to the right value
will not be the method that we use now (it will probably be a declaration
or pragma that modifies an existing proc_info, not a way of creating
new proc_infos). I don't think that saving this field will make any such
change later at all easier.

I have followed your other suggestions.

mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au

More information about the developers mailing list