StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16727199
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-24T03:22:09.480
FavoriteCount
0
LastActivityDate
2013-05-24T05:06:59.663
LastEditDate
2013-05-24T05:06:59.663
LastEditorUserId
1234550
OwnerUserId
1234550
ParentId
16726111
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
This is difficult to do cleanly in Fortran 90. It is straight forward in Fortran 2003. Resolution of the procedure to call when the generic reference <code>fun</code> is encountered (in <code>CALL fun(pt)</code>) is done at compile time, based on the declared type of <code>pt</code>. If you are limited to Fortran 90, then effectively you will need to maintain a flag of some sort that indicates at runtime which particular derived type you want to work with, have a named object for each of type A and type B, and everytime you want to reference <code>fun</code> have an IF construct that selects the correctly named argument. (If the size of the objects is significant you can arrange for them to have common storage.) Something like: <pre><code>TYPE(A) :: pt_A TYPE(B) :: pt_B ... IF (input .EQ. 'A') THEN CALL fun(pt_A) ELSE CALL fun(pt_B) END IF </code></pre> In F2003, you would define a common parent type, that had a specific binding named fun. <code>pt</code> would then be a polymorphic allocatable object, allocated based on input to either type A or type B as appropriate. <pre><code>TYPE :: Parent CONTAINS PROCEDURE(parent_Fun), DEFERRED :: Fun END TYPE Parent ABSTRACT INTERFACE SUBROUTINE parent_Fun(obj) IMPORT :: Parent IMPLICIT NONE CLASS(Parent), INTENT(IN) :: obj END SUBROUTINE parent_Fun END INTERFACE TYPE, EXTENDS(Parent) :: A REAL :: x, y CONTAINS PROCEDURE :: A => A_Fun END TYPE A TYPE, EXTENDS(Parent) :: B INTEGER :: x, y CONTAINS PROCEDURE :: B => B_Fun END TYPE B CLASS(Parent), ALLOCATABLE :: pt ... IF (input .EQ. 'A') THEN ALLOCATE(A:: pt) ELSE ALLOCATE(B:: pt) END IF ... CALL pt%Fun() </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFortran90 assigning pointers and derived types at runtime
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USIanH
UserOwnerUserId
1. USIanH
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POFortran90 assigning pointers and derived types at runtime
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.