No variable instantiations about bridges-cxx HOT 5 CLOSED

Taken care of most of these(in constructors, mostly), except template type members, which are difficult to initialize -- there seems to be lots of discussions on this on stack overflow.

from bridges-cxx.

As I understand it, a class' default constructor is always called, but this isn't true for built in types, as they may be anything. For example int a; will likely leave a=0, but it isn't guaranteed. But if a "constructor" is called, for example int a=int(); it will explicitly be default value initialized.

This applies to template parameters as well: E e = E(); and K key = K();

from bridges-cxx.

template param initializations fixed.. dont see the uninitialized variables in ElementVisualizer or LinkVisualizer.

from bridges-cxx.

ElementVisualizer doesn't default initialize the "key" value, but this isnt really a problem as there is no getfunction.

LinkVisualizer doesn't default initialize the "weight" value, and because there is a getfunction, this will lead to an empty string being set and returned for weight, if it isn't set before a get call, which would be problematic.

The others look good though.

from bridges-cxx.

Good catch, will fix (linkvisualizer)..

 -- krs

On 11/17/15 3:58 PM, Dakota Carmer wrote:

ElementVisualizer doesn't default initialize the "key" value, but this
isnt really a problem as there is no getfunction.

LinkVisualizer doesn't default initialize the "weight" value, and
because there is a getfunction, this will lead to an empty string
being set and returned for weight, if it isn't set before a get call,
which would be problematic.

The others look good though.

—
Reply to this email directly or view it on GitHub
#4 (comment).

Kalpathi Subramanian Ph: 704 687 8579
Associate Professor Email: [email protected]
Dept of Computer Science Web:http://webpages.uncc.edu/~krs
The University of North Carolina
Charlotte, NC 28202-0001

from bridges-cxx.