Re: Parsing challenge to reduce blanks
- From: "James Van Buskirk" <not_valid@xxxxxxxxxxx>
- Date: Tue, 2 Aug 2005 14:56:06 -0600
"David Frank" <dave_frank@xxxxxxxxxxx> wrote in message
news:nbQHe.9334$6f.6929@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> adding 1 trailing blank to a function's otherwise exact returned length
> wont be a problem in F2003 syntax,
> since
> character(:),allocatable :: outline will be legal
But it makes the most sense to me for the function itself to
detect whether that trailing blank should be inserted and to
insert it if required without the need for further processing.
How useful would cos(x) be if you had to check whether the
input was some special value like pi/5 so you would in that
case have to substitute the correct value of (1+sqrt(5))/4
rather than just be able to accept the value of cos(x) without
further processing?
--
write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, &
6.0134700243160014d-154/),(/'x'/)); end
.
- Follow-Ups:
- Re: Parsing challenge to reduce blanks
- From: FJRA
- Re: Parsing challenge to reduce blanks
- References:
- Parsing challenge to reduce blanks
- From: David Frank
- Re: Parsing challenge to reduce blanks
- From: David Frank
- Re: Parsing challenge to reduce blanks
- From: James Van Buskirk
- Re: Parsing challenge to reduce blanks
- From: David Frank
- Re: Parsing challenge to reduce blanks
- From: James Van Buskirk
- Re: Parsing challenge to reduce blanks
- From: David Frank
- Re: Parsing challenge to reduce blanks
- From: David Frank
- Parsing challenge to reduce blanks
- Prev by Date: Re: Parsing challenge to reduce blanks
- Next by Date: Re: Parsing challenge to reduce blanks
- Previous by thread: Re: Parsing challenge to reduce blanks
- Next by thread: Re: Parsing challenge to reduce blanks
- Index(es):
Relevant Pages
|