Talk:PurifyPlus

message: The article should discuss differences between Purify and Valgrind, etc., not just Purify and traditional debuggers (maybe memory debuggers in abstract should have a separate page). Even though Valgrind is mentioned the rest of the article acts like Purify is one-of-a-kind, which is definitely not true. 12.206.192.225 (talk) 14:46, 5 April 2008 (UTC)
thread_title: Differences

message: I think languages like Java and C# can have memory leaks as well, though not in the traditional way of speaking.  If you have a list of object, but never remove objects that won't be used, that could be considered a memory leak as well.  Profiling tools can help locate these sorts of problems.
:Thats true, but as a programmer in several high and low level languages, I would not call that a memory leak.  IMHO, the term "leak" implies that the memory leaks out of the system, pernamently lost and never to be recovered.  Holding references to a bunch of unused objects is just bloat, and while profilers help identify bloat, its different from a leak. --Bletch 00:08, 28 Dec 2004 (UTC)
replies: text: I agree.  I've edited the page to remove that line.  --Jhayman 04:05, 13 July 2006 (UTC)
thread_title: Managed leaks

message: I put the cleanup tag on this page because it needs some work. It currently needs to be structured into sections and large chunks need to be rewritten to make it read more like an encyclopedia instead of a commentary or review of the software. --Dr. WTF 20:32, 10 February 2007 (UTC)
thread_title: Cleanup

message: The article currently makes reference to memory-managed languages not being able to have memory leaks, followed by a statement that these languages do have memory leaks. I have tried to rectify this. The fact that Rational supports Java  ought to say something about the existence of memory leaks... -Fuzzy 15:25, 26 April 2007 (UTC)
thread_title:  Purify and Java 

message: :Image:Purify Logo.png is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If there is  other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page.  Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.
BetacommandBot (talk) 17:38, 5 December 2007 (UTC)
thread_title: Fair use rationale for Image:Purify Logo.png

message: Purify worked with SUN Fortran on SPARC about a decade ago. Jmath666 (talk) 23:53, 14 October 2009 (UTC)
thread_title:  Purify and Fortran 

message: Are there plans to release a supported version of Purify to run on Red Hat Enterprise version 6.x ?  (11 Sept 2012)  — Preceding unsigned comment added by 63.239.65.11 (talk) 19:46, 11 September 2012 (UTC)
thread_title:  Purify and RHEL 6.x