forums.silverfrost.com

MarzAttax · Joined: 15 Jun 2006 Posts: 46

Something I came across whilst writing the code for my post in Support=>Time, was that if I incorrectly had the following in one of my modules:

Module Animal_hdr

Type stColours
Integer*1, Pointer i1Colour(:)
End Type stColours

Type stStripes
Type(stColours), Pointer :: pstStripe(:, :)
EndType stStripes

Type stZebras
Type(stLion), Pointer :: pstZebra(:, :)
Integer*4 :: iOffsetLargeX, iOffsetLargeY
EndType stZebras

End Module Animal_hdr

then the project would still build. It appeared to not have detected that there is no such definition as stLion. The project builds, but unsurprisingly "bombs" upon execution when I attempt to allocate the arrays :o)

Marz

MarzAttax · Joined: 15 Jun 2006 Posts: 46

Nothing?
Is it a known issue?
Am I just being silly with this or something?

Marz

PaulLaidler · Posted: Tue Nov 20, 2012 5:30 pm Post subject:

This is a compiler fault and I have logged it for investigation.

MarzAttax · Joined: 15 Jun 2006 Posts: 46

PaulLaidler · Posted: Sat Jul 20, 2013 4:41 pm Post subject:

I will see if I can speed this one up.

PaulLaidler · Posted: Sat Jul 27, 2013 7:24 am Post subject:

I can confirm that there is a bug here. FTN95 should complain that stLoin has not been defined. It will complain later when you try to use stLoin so this is not show-stopping. However, I have logged this as some thing that needs to be fixed.

MarzAttax · Joined: 15 Jun 2006 Posts: 46

Hi there,

Thanks for the reply.

However, I have again just spent an entire day (actually only 12hrs straight so far - I have spent 3 days tracking it down before now) trying to track down an issue that I suspect is related to this.

When my code has this "error" in it, it usually exhibits behavior such as not populating structures properly in other areas of the code (anticipate memory corruption/alignment issue because of it).

The upshot of this is that even though I am not using the offending structure in the place my code fails, my code still will not run Sad

Any updates on the progress of fixing this is very much appreciated.

TIA

Marz

PaulLaidler · Posted: Sat Feb 08, 2014 9:27 am Post subject:

There is no progress so far. It is on a list that we are working through.
However, this is not a significant issue and ought not to limit your development process.

PaulLaidler · Posted: Thu Mar 20, 2014 11:29 am Post subject:

This has now been fixed for the next release.