Re: ENTRY statement
- From: nmm1@xxxxxxxxx
- Date: Tue, 6 Oct 2009 10:07:34 +0100 (BST)
In article <7ivhllF3135fiU1@xxxxxxxxxxxxxxxxxx>,
Steve Lionel <steve.lionel@xxxxxxxxxxxxx> wrote:
When we developed the DEC Fortran 90 compiler, from a different code
base, a different method was used which did not have any sort of
"memory" of past arguments, and a lot of customers found that their
broken code was now really broken.
Yup :-) We had a lot of customers who switched between IBM and DEC,
and a FAQ was "Why doesn't my program work on the other?" This one
wasn't one of the main causes, but wasn't rare - and it could cause
failure in both directions, depending on the type of brokenness in
the code.
Regards,
Nick Maclaren.
.
- References:
- Re: ENTRY statement
- From: David Weatherall
- Re: ENTRY statement
- From: Richard Maine
- Re: ENTRY statement
- From: Steve Lionel
- Re: ENTRY statement
- Prev by Date: Re: Alan Miller's statistical software collection - gone?
- Next by Date: Re: Array argument bounds checking
- Previous by thread: Re: ENTRY statement
- Next by thread: Re: Order of procedure argument eval?
- Index(es):