c++ - delete right child makes parent left pointer point to nullptr -


thank checking question, have basic question on operator "delete", seems can automatically change pointer value nullptr. let me give example this:

    template <typename t>     void tree<t>::remove(const unsigned& index, treenode<t>*& tree)     {         if(tree == nullptr)         {             std::cerr << "remove: can't find target" << std::endl;         }         else if(index < tree->index)         {             remove(index, tree->left);         }         else if(index > tree->index)         {             remove(index, tree->right);         }         else if(index == tree->index)         {             if(tree->degree() == 2)             {                 tree->index = findmin(tree->right)->index;                 tree->value = findmin(tree->right)->value;                 remove(tree->index, tree->right);             }             else             {                 auto oldnode = tree;                 tree = (tree->left != nullptr) ? tree->left: tree->right;                 delete oldnode;     //          oldnode = nullptr;              }         }     }

the code above classic searching tree remove algorithm. if current tree has 2 nodes root (with key equals 3 example) , right child (with key equals 4 example), when remove node 4, call remove twice , go line:

    delete oldnode;

and line delete "oldnode", should 4 right now. far knowledge, delete operator free memory address(the address same value of oldnode), means tells os address available again. suppose when print out value of root's right pointer(root->right), should address. when print out 0. question when root->right changed?

hope explain question clearly. may stupid question, let me known if make confusion.

i think seeing use of pointer after delete undefined behavior (until c++14).

for c++14: indirection through pointer became invalid in manner , passing deallocation function (double-delete) undefined behavior. other use implementation-defined.

undefined behavior allows implementation whatever wants pointer after delete (even change value).

it looks implementation sets value of pointer nullptr in delete.


-

Popular posts from this blog

Apache NiFi ExecuteScript: Groovy script to replace Json values via a mapping file -

i working apache nifi 0.5.1 on groovy script replace incoming json values ones contained in mapping file. mapping file looks (it simple .txt): header1;header2;header3 a;some text;a2 i have started following: import groovy.json.jsonbuilder import groovy.json.jsonslurper import java.nio.charset.standardcharsets def flowfile = session.get(); if (flowfile == null) { return; } flowfile = session.write(flowfile, { inputstream, outputstream -> def content = """ { "field1": "a" "field2": "a", "field3": "a" }""" def slurped = new jsonslurper().parsetext(content) def builder = new jsonbuilder(slurped) builder.content.field1 = "a" builder.content.field2 = "some text" builder.content.field3 = "a2" outputstream.write(builder.toprettystring().ge...
Read more

node.js - How do I prevent MongoDB replica set from querying the primary? -

read-operations-only: is there way have mongodb replica set, make mongodb instance on box connected to, mongodb gets queried? i have 3 ec2 instances behind aws load balancer. on each ec2 instance runs mongodb, part of replica set. i have express endpoints on nodejs , connect replica set follows mongodb.mongoclient.connect('mongodb://1.1.1.1,2.2.2.2,3.3.3.3.', function (err, db) { if (err) { complete('{}'); } else { i distribute load of queries evenly across 3 instances of mongodb replica set instead of default having queries routed ec2 instance primary mongodb defined, because destroys point of load balancer (which balance load of queries across 3 instances evenly). my understanding when connecting mongodb replica set, primary instance selected unless primary instance down, , therefore purpose of every secondary instance serve backup. in example people call hot,cold,cold. because there 2...
Read more