Re: Integer Coersion
- From: Brooks Moses <bmoses-nospam@xxxxxxxxxxxxxxxxxx>
- Date: Sat, 10 Feb 2007 01:44:48 -0800
PJH wrote:
Someone around here is going to get hot under the collar with you for saying
that INTEGER(1) implies 1 byte, rather than INTEGER*1. I'm sure there
actully are some compilers out there that deliberately don't have a
KIND=BYTE equivalence.
G77 used INTEGER(1) to mean the default integer, INTEGER(2) as something occupying twice the space, INTEGER(5) as something occupying half the space, and INTEGER(7) as the system pointer type.
- Brooks
--
The "bmoses-nospam" address is valid; no unmunging needed.
.
- Follow-Ups:
- Re: Integer Coersion
- From: Gary Scott
- Re: Integer Coersion
- References:
- Integer Coersion
- From: PJH
- Re: Integer Coersion
- From: David Frank
- Re: Integer Coersion
- From: PJH
- Re: Integer Coersion
- From: David Frank
- Re: Integer Coersion
- From: PJH
- Integer Coersion
- Prev by Date: Re: acquiring standard
- Next by Date: help with an error
- Previous by thread: Re: Integer Coersion
- Next by thread: Re: Integer Coersion
- Index(es):