Hi Colin, no, Nuke doesn't overload new/delete so any STL containers you use won't have their memory tracked by Nuke. There is a header in DDImage called STLAllocator.h that has an STL allocator that calls into DD::Image::Memory, as well as a couple of typedef's for vector and deque.
Hope that helps... On Thu, Jun 14, 2012 at 6:53 AM, Colin Doncaster <colin.doncas...@gmail.com>wrote: > Hi there - > > I'm looking at DD::Image::Memory and was wondering how standard template > containers ( vector, map, etc. ) fit within this context? I assume > new/delete is overloaded and the templates still happily report their usage > or do we need to explicitly call allocate? > > This is what we're assuming, but is that correct? > > Thanks_______________________________________________ > Nuke-dev mailing list > Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev > -- Tom Ward, Software Engineer The Foundry, 6th Floor, The Communications Building, 48 Leicester Square, London, UK, WC2H 7LT Tel: +44 (0)20 7434 0449 Web: www.thefoundry.co.uk The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027
_______________________________________________ Nuke-dev mailing list Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
