You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by @AnsleyManke on 20 Jan 2005 20:53 UTC
The array line_mem stores irregularly-spaced coordinates for all lines, plus
their cell boundaries. (See bug 767). Does it make sense to use dynamic memory
allocation for this? The problem is that when we find we need more coordinate
storage, we need to keep existing coordinate data that may already have been
loaded. This is unlike pplus dynamic memory, where we allocate memory before
loading data and sending it to pplus, so any existing data can be wiped out by a
free command.
Reported by @AnsleyManke on 20 Jan 2005 20:53 UTC
The array line_mem stores irregularly-spaced coordinates for all lines, plus
their cell boundaries. (See bug 767). Does it make sense to use dynamic memory
allocation for this? The problem is that when we find we need more coordinate
storage, we need to keep existing coordinate data that may already have been
loaded. This is unlike pplus dynamic memory, where we allocate memory before
loading data and sending it to pplus, so any existing data can be wiped out by a
free command.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1158
The text was updated successfully, but these errors were encountered: