Note that there are some explanatory texts on larger screens.

plurals
  1. USSyndacate
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COYes, thank you, Joachim. I mentioned the default visibility in my question. I am aware that structs exist in C++ to be backwards compatible with C. I was curious if you gained any performance benefits - if structs in C++ weren't mangled to be classes then they should simply be chunks of contiguously allocated memory - as they were in C. It would be nice if they weren't changed to be classes. Though it looks like there aren't any performance benefits to be gained from using structs in C++, which is quite unfortunate. Structs could be very useful in C++ if they didn't have the overhead.
      singulars
    2. COYes, I know it was inherited from C. That wasn't the aim of my question - at all. I was wondering if you gained anything from using structs in C++, when they were 'messed up' (at least in my opinion) opposed to how they were in C. Structs in C aren't the same as structs in C++, despite the backwards compatibility, and given that they have the same exact aspects as classes, I was wondering if you gained anything by using them. I really wish structs in C++ would remain as they were in C, simply contiguous allocations of data, no functions, no visibility, no anything - just variables.
      singulars
    3. COHow unfortunate that it's re-defined as a copy of the list member. I believe it would be much more useful to show up as a reference, as if you were setting it, it would probably be to manipulate the structure in some way or another. I tested the syntax: `for idx in range(0, len(my_list)): my_list[idx] = new_obj` It works to my liking. Thank you.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload