Re: Who uses clapack?

From: Jan Vorbrüggen (jvorbrueggen-not_at_mediasec.de)
Date: 12/13/04 

Date: Mon, 13 Dec 2004 11:43:11 +0100

> Interoperability between languages is a gray area where one
> needs to consider the following:
> 1 Ability to suppress C++ name decoration, knowledge of other
> conventions such as underscores appended or prepended to name
> 2 Knowledge of linker conventions such as upper case conversion
> and maximum name length
> 3 Ability for the programmer to specify parameter passing by
> address and by value which C and C++ have
> 4 Ability for the user to use parameter passing from left to
> right or vice versa
> 5 Conventions on stack based parameter passing notably padding
> and stack alignment
> 6 Decide on who resets the stack pointer, caller or callee.

You lack historical perspective. Coming from a DEC world, I was surprised
to learn that there existed systems where mixing source from different
languages in one application was not the norm, not say the rarest of
exceptions fraught with difficulties and pain - and all of that for no
perceptible reason at all but perhaps a bad case of NIH syndrome.

Although I must admit they didn't deem C++ important enough to re-write
the linker from scratch to avoid name mangling. However, the support tools
were quite good in that respect.

        Jan

Relevant Pages

  • Re: Who uses clapack?
    ... > Interoperability between languages is a gray area where one ... > 2 Knowledge of linker conventions such as upper case conversion ... > 3 Ability for the programmer to specify parameter passing by ... > 5 Conventions on stack based parameter passing notably padding ...
    (comp.lang.fortran)
  • Re: Use of ; in Forth Compiler
    ... >Languages that use more conventional parameter passing strategies have ... >overhead on entering and leaving subroutines consisting of the code to ... setting up stack frames and taking them ...
    (comp.lang.forth)
  • Re: OT: compilers, interpreters, and VMs
    ... These conventions are unsuitable for a vast number ... Unsuitable for dynamic typing (data representation is ... unsuitable for safe languages (heavily relies on ... associating the size of an array with the array, stack overflow is ...
    (comp.lang.misc)
  • Re: Order of stack items
    ... By following the conventions, ... the word SIGN in number conversions takes a signed ... expected its argument in the 3rd cell on the stack, and started with a ROT. ...
    (comp.lang.forth)
  • Re: Breaking backwards compatibility - good or bad?
    ... languages here - not HUMAN languages. ... Case distinction is but one of the many distinctions and pernickity rules that we have to learn when we learn to program in a language or system that uses it. ... But I find that in practice there are lots of different conventions and I'm often switching from one to another as I work on different scripts written by different people at different times, ...
    (comp.lang.php)
Loading