U++ framework: U++ Developers corner » Question about pick behaviour

Home » Developing U++ » U++ Developers corner » Question about pick behaviour

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Re: Question about pick behaviour [message #31828 is a reply to message #31804]

Wed, 30 March 2011 10:44

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

Report message to a moderator

[Message index]

		Question about pick behaviour By: ross_tang on Mon, 28 March 2011 11:25
		Re: Question about pick behaviour By: mirek on Mon, 28 March 2011 12:56
		Re: Question about pick behaviour By: mr_ped on Mon, 28 March 2011 16:23
		Re: Question about pick behaviour By: ross_tang on Tue, 29 March 2011 04:20
		Re: Question about pick behaviour By: kohait00 on Wed, 30 March 2011 10:44

Previous Topic:	Google Summer of Code
Next Topic:	Redmine Tasks

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Jun 30 18:06:55 GMT+2 2026

Total time taken to generate the page: 0.00427 seconds