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 #31800 is a reply to message #31793]

Mon, 28 March 2011 16:23

mr_ped
Messages: 826
Registered: November 2005
Location: Czech Republic - Praha

Experienced Contributor

ross_tang: once your two references would start to live in quite different parts of complex app on their own, it would be quite difficult to decide which one is responsible to finish life cycle of that memory block, ie. you would need GC to make the life easier. Which means you failed to find an U++ way of design where you know where that memory block belongs and when you are done with it and you can lost it completely, so there's no need for GC, you just exit from that stack window away.

It means U++ gives less freedom in implementation to force you for a bit more thoughtful design in exchange for no GC performance penalty and the final source is usually simpler and easier to maintain.

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: Mon Jun 29 16:27:09 GMT+2 2026

Total time taken to generate the page: 0.00438 seconds