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 » Developing U++ » U++ Developers corner » Question about pick behaviour
Re: Question about pick behaviour [message #31828 is a reply to message #31804] Wed, 30 March 2011 10:44 Go to previous message
kohait00 is currently offline  kohait00
Messages: 939
Registered: July 2009
Location: Germany
Experienced Contributor
mr_ped is absolutely right..

finally, U++ is agressive C++, which avoids speed penalties at any price Smile GC is not available here and we have to deal with objects differently. U++ fundamental design rule (see manual somewhere) is everything belongs somewhere.. so at any time in any point of code you are able to determine what actually is under *your* (current inspected object's) control and responsibility.

if you are on doing python / U++ intefacing (we might join on that, i'm currently preparing/doing it) the only thing usefull for interfacing is U++ Value, as the counterpart to PyObject, since it uses Object counting/referencing internally, without GC though
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Google Summer of Code
Next Topic: Redmine Tasks
Goto Forum:
  


Current Time: Sun Aug 24 16:53:06 CEST 2025

Total time taken to generate the page: 0.04808 seconds