Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
libmtime
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
icon-libraries
libmtime
Commits
881ec5c0
Commit
881ec5c0
authored
8 years ago
by
Florian Prill
Browse files
Options
Downloads
Plain Diff
Merge branch 'feature-hl' of git.mpimet.mpg.de:libmtime into feature-hl
parents
4492ac67
f435144a
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/libmtime_hl.f90
+23
-3
23 additions, 3 deletions
src/libmtime_hl.f90
with
23 additions
and
3 deletions
src/libmtime_hl.f90
+
23
−
3
View file @
881ec5c0
...
...
@@ -31,11 +31,23 @@ module mtime_hl
contains
! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! The use of "final" is "potentially" dangerous - it is supported,
! e.g., on gfortran 4.9 only partially. (see
! http://fortranwiki.org/fortran/show/Fortran+2003+status)
!
! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
! final :: t_datetime_deallocate
!
! final is required to prevent memory leaks, when variables go out
! of scope. So this routine will get called only in this case and
! the call is introduced by the compiler - nobody will see those.
! So I will reenable the final but not for gcc odler than gcc5.
!
! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#if __GNUC__ > 4
final
::
t_datetime_deallocate
#endif
procedure
::
to_string
=>
t_datetime_to_string
procedure
::
assign_string
=>
t_datetime_assign_string
...
...
@@ -73,8 +85,9 @@ module mtime_hl
contains
! final :: t_timedelta_deallocate
#if __GNUC__ > 4
final
::
t_timedelta_deallocate
#endif
procedure
::
to_string
=>
t_timedelta_to_string
procedure
::
assign_string
=>
t_timedelta_assign_string
...
...
@@ -85,13 +98,20 @@ module mtime_hl
contains
! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! In my opinion, this deallocate does not make sense, since the
! this%dt data member is a simply derived type (with C conforming
! kind values). The necessary deallocates happen in the wrapper
! routines, where a POINTER variable is used and its contents are
! copied to this%dt.
!
! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! You're right, but this routine is just the implementation of
! final, and no user should call it explicitly! BUt of course,
! you need to make the call available.
!
! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
subroutine
t_datetime_deallocate
(
this
)
type
(
t_datetime
),
target
,
intent
(
inout
)
::
this
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment