Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ Core » Using Vector::At doesn't initialize implicit types
Re: Using Vector::At doesn't initialize implicit types [message #17124 is a reply to message #17113] Tue, 29 July 2008 18:39 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 14267
Registered: November 2005
Ultimate Member
cbpporter wrote on Tue, 29 July 2008 10:03

Well I guess we can leave it as is for performance reasons, but then we should add an entry to "U++ traps and pitfalls". This behavior should be documented somewhere, made very clear especially for pointers. Using pointers in Vector is not that common, so when you start using them it can be a nasty surprise that the values are not null checkable.


I do not know. If you do not initialize variable, you can consider it unitialized. If you do not initialize struct members, ditto.

What is surprising on At behaviour? Especially if it has another "init" method variant.

But OK, you are perhaps right.

Mirek
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: zlib
Next Topic: Interesting struggle with "Moveable<T>" usage in GCC
Goto Forum:
  


Current Time: Wed Aug 27 19:43:26 CEST 2025

Total time taken to generate the page: 0.05509 seconds