Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Z
zmap
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ensembl-gh-mirror
zmap
Commits
0a05b62b
Commit
0a05b62b
authored
20 years ago
by
edgrif
Browse files
Options
Downloads
Patches
Plain Diff
superceded by one in src.
parent
90b0c84b
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
src/zmapThreads/TODO
+0
-9
0 additions, 9 deletions
src/zmapThreads/TODO
src/zmapView/TODO
+0
-18
0 additions, 18 deletions
src/zmapView/TODO
with
0 additions
and
27 deletions
src/zmapThreads/TODO
deleted
100755 → 0
+
0
−
9
View file @
90b0c84b
- need to introduce pthreads_cancel_points into the code so that a cancel
will interrupt at good places....some thought needed here though to ensure
that we don't just litter the code with cancel points making it hard to
maintain...
I think to some extent the main network reading calls get interrupted by
a cancel so that makes it all work better.
This diff is collapsed.
Click to expand it.
src/zmapView/TODO
deleted
100755 → 0
+
0
−
18
View file @
90b0c84b
The merge is not as simple as I thought, need to either copy everything that is to be merged
(seems wasteful) or we need to NULL out/remove the things we have transferred....perhaps not
so hard....
Main thing is to protect whole GDatas that we move into our new sets and null out ones we
don't want. But also, what happens to datastructs of features that we have allocated but
no longer need...they should be freed....
Sounds like merge needs to be in some separate feature code package....
It can be done but needs thought..........
Currently we just don't free the stuff...and we should leave it like this for ISMB.
This must be sorted out afterwards otherwise it will use up a lot of memory.
This diff is collapsed.
Click to expand it.
Preview
0%
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