ruby-prof 0.14.1 → 0.14.2

data/CHANGES

@@ -1,6 +1,6 @@
-0.14.0 (2014-01-04)
+0.14.2 (2014-01-05)
 ======================
-* fix compile problem under Windows
+* hopefully fixed compile problem under Windows
 
 0.14.0 (2014-01-02)
 ======================

data/Rakefile

@@ -75,10 +75,10 @@ RDoc::Task.new("rdoc") do |rdoc|
   rdoc.rdoc_dir = 'doc'
   rdoc.title    = "ruby-prof"
   # Show source inline with line numbers
-  rdoc.options << "--inline-source" << "--line-numbers"
+  rdoc.options << "--line-numbers"
   # Make the readme file the start page for the generated html
   rdoc.options << '--main' << 'README.rdoc'
-  rdoc.rdoc_files.include('bin/**/*',
+  rdoc.rdoc_files.include('bin/*',
                           'doc/*.rdoc',
                           'examples/flat.txt',
                           'examples/graph.txt',
@@ -92,13 +92,17 @@ end
 
 task :default => :test
 
-for file in Dir['**/*.{o,so,bundle}']
+for file in Dir['lib/**/*.{o,so,bundle}']
   CLEAN.include file
 end
-
-for file in Dir['tmp/*.{txt,dat,png,html}']
+for file in Dir['doc/**/*.{txt,dat,png,html}']
   CLEAN.include file
 end
+CLEAN.reject!{|f| !File.exist?(f)}
+task :clean do
+  # remove tmp dir contents completely after cleaning
+  FileUtils.rm_rf('tmp/*')
+end
 
 desc 'Run the ruby-prof test suite'
 Rake::TestTask.new do |t|

data/doc/LICENSE.html

@@ -93,11 +93,11 @@ this list of conditions and the following disclaimer in the documentation
 and/or other materials provided with the distribution.</p>
 </li></ol>
 
-<p>THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS&#39;&#39;
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+<p>THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS” AND ANY
+EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
 CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

data/doc/README_rdoc.html

@@ -142,8 +142,8 @@ href="README_rdoc.html">README</a>.</p>
 
 <p>ruby-prof requires Ruby 1.9.3 or higher.</p>
 
-<p>If you are running Linux or Unix you&#39;ll need a C compiler so the
-extension can be compiled when it is installed.</p>
+<p>If you are running Linux or Unix you’ll need a C compiler so the extension
+can be compiled when it is installed.</p>
 
 <p>If you are running Windows, then you may need to install the Windows
 specific RubyGem which includes an already built extension (see Install
@@ -155,8 +155,8 @@ section).</p>
 
 <pre>gem install ruby-prof</pre>
 
-<p>If you&#39;re on windows then a prebuilt binary gem is available.  You may
-of course compile it yourself via use of devkit on MinGW.</p>
+<p>If you’re on windows then a prebuilt binary gem is available.  You may of
+course compile it yourself via use of devkit on MinGW.</p>
 
 <h2 id="label-Usage">Usage<span><a href="#label-Usage">&para;</a> <a href="#documentation">&uarr;</a></span></h2>
 
@@ -173,7 +173,7 @@ For more information refer to the documentation of the ruby-prof command.</p>
 <p>The second way is to use the ruby-prof API to profile particular segments
 of code.</p>
 
-<pre class="ruby"><span class="ruby-identifier">require</span> <span class="ruby-string">&#39;ruby-prof&#39;</span>
+<pre class="ruby"><span class="ruby-identifier">require</span> <span class="ruby-string">'ruby-prof'</span>
 
 <span class="ruby-comment"># Profile the code</span>
 <span class="ruby-constant">RubyProf</span>.<span class="ruby-identifier">start</span>
@@ -189,7 +189,7 @@ of code.</p>
 
 <p>Alternatively, you can use a block to tell ruby-prof what to profile:</p>
 
-<pre class="ruby"><span class="ruby-identifier">require</span> <span class="ruby-string">&#39;ruby-prof&#39;</span>
+<pre class="ruby"><span class="ruby-identifier">require</span> <span class="ruby-string">'ruby-prof'</span>
 
 <span class="ruby-comment"># Profile the code</span>
 <span class="ruby-identifier">result</span> = <span class="ruby-constant">RubyProf</span>.<span class="ruby-identifier">profile</span> <span class="ruby-keyword">do</span>
@@ -205,7 +205,7 @@ of code.</p>
 
 <p>ruby-prof also supports pausing and resuming profiling runs.</p>
 
-<pre class="ruby"><span class="ruby-identifier">require</span> <span class="ruby-string">&#39;ruby-prof&#39;</span>
+<pre class="ruby"><span class="ruby-identifier">require</span> <span class="ruby-string">'ruby-prof'</span>
 
 <span class="ruby-comment"># Profile the code</span>
 <span class="ruby-constant">RubyProf</span>.<span class="ruby-identifier">start</span>
@@ -220,7 +220,7 @@ of code.</p>
 <p>Note that resume will automatically call start if a profiling run has not
 yet started.  In addition, resume can also take a block:</p>
 
-<pre class="ruby"><span class="ruby-identifier">require</span> <span class="ruby-string">&#39;ruby-prof&#39;</span>
+<pre class="ruby"><span class="ruby-identifier">require</span> <span class="ruby-string">'ruby-prof'</span>
 
 <span class="ruby-comment"># Profile the code</span>
 <span class="ruby-constant">RubyProf</span>.<span class="ruby-identifier">resume</span> <span class="ruby-keyword">do</span>
@@ -240,10 +240,10 @@ results. This is useful for reducing connectivity in the call graph, making
 it easier to identify the source of performance problems when using a graph
 printer.</p>
 
-<p>For example, consider Integer#times: it&#39;s hardly ever useful to know
-how much time is spent in the method itself. We&#39;re much more interested
-in how much the passed in block contributes to the time spent in the method
-which contains the Integer#times call.</p>
+<p>For example, consider Integer#times: it’s hardly ever useful to know how
+much time is spent in the method itself. We’re much more interested in how
+much the passed in block contributes to the time spent in the method which
+contains the Integer#times call.</p>
 
 <p>Methods are eliminated from the collected data by calling
 `eliminate_methods!` on the profiling result, before submitting it to a
@@ -270,10 +270,9 @@ profiling.</p>
 
 <h2 id="label-Benchmarking+full+load+time+including+rubygems+startup+cost+%3D%3D">Benchmarking full load time including rubygems startup cost ==<span><a href="#label-Benchmarking+full+load+time+including+rubygems+startup+cost+%3D%3D">&para;</a> <a href="#documentation">&uarr;</a></span></h2>
 
-<p>If you want to get a more accurate measurement of what takes all of a
-gem&#39;s bin/xxx command to load, you may want to also measure
-rubygems&#39; startup penalty. You can do this by calling into
-bin/ruby-prof directly, ex:</p>
+<p>If you want to get a more accurate measurement of what takes all of a gem’s
+bin/xxx command to load, you may want to also measure rubygems’ startup
+penalty. You can do this by calling into bin/ruby-prof directly, ex:</p>
 
 <p>$ gem which ruby-prof</p>
 
@@ -291,28 +290,26 @@ g:192binsome_installed_gem_command</p>
 
 <h2 id="label-Profiling+Tests">Profiling Tests<span><a href="#label-Profiling+Tests">&para;</a> <a href="#documentation">&uarr;</a></span></h2>
 
-<p>ruby-prof supports profiling tests cases written using Ruby&#39;s built-in
-unit test framework (ie, test derived from Test::Unit::TestCase).  To
-enable profiling simply add the following line of code to within your test
-class:</p>
+<p>ruby-prof supports profiling tests cases written using Ruby’s built-in unit
+test framework (ie, test derived from Test::Unit::TestCase).  To enable
+profiling simply add the following line of code to within your test class:</p>
 
 <pre>include RubyProf::Test</pre>
 
 <p>Each test method is profiled separately.  ruby-prof will run each test
 method once as a warmup and then ten additional times to gather profile
 data. Note that the profile data will <strong>not</strong> include the
-class&#39;s setup or teardown methods.</p>
+class’s setup or teardown methods.</p>
 
 <p>Separate reports are generated for each method and saved, by default, in
-the test process&#39;s working directory.  To change this, or other
-profiling options, modify your test class&#39;s PROFILE_OPTIONS hash table.
-To globally change test profiling options, modify
-RubyProf::Test::PROFILE_OPTIONS.</p>
+the test process’s working directory.  To change this, or other profiling
+options, modify your test class’s PROFILE_OPTIONS hash table. To globally
+change test profiling options, modify RubyProf::Test::PROFILE_OPTIONS.</p>
 
 <h2 id="label-Profiling+Rails">Profiling Rails<span><a href="#label-Profiling+Rails">&para;</a> <a href="#documentation">&uarr;</a></span></h2>
 
 <p>To profile a Rails application it is vital to run it using production like
-settings (cache classes, cache view lookups, etc.).  Otherwise, Rail&#39;s
+settings (cache classes, cache view lookups, etc.).  Otherwise, Rail’s
 dependency loading code will overwhelm any time spent in the application
 itself (our tests show that Rails dependency loading causes a roughly 6x
 slowdown).  The best way to do this is create a new Rails environment,
@@ -328,14 +325,14 @@ likely turn off caching.</p>
 <p>Add the ruby-prof to your gemfile:</p>
 
 <pre>group :profile do
-  gem &#39;ruby-prof&#39;
+  gem 'ruby-prof'
 end</pre>
 </li><li>
 <p>Add the ruby prof rack adapter to your middleware stack.  One way to do
 this is by adding the following code to config.ru:</p>
 
 <pre class="ruby"><span class="ruby-keyword">if</span> <span class="ruby-constant">Rails</span>.<span class="ruby-identifier">env</span>.<span class="ruby-identifier">profile?</span>
-  <span class="ruby-identifier">use</span> <span class="ruby-constant">Rack</span><span class="ruby-operator">::</span><span class="ruby-constant">RubyProf</span>, :<span class="ruby-identifier">path</span> =<span class="ruby-operator">&gt;</span> <span class="ruby-string">&#39;/temp/profile&#39;</span>
+  <span class="ruby-identifier">use</span> <span class="ruby-constant">Rack</span><span class="ruby-operator">::</span><span class="ruby-constant">RubyProf</span>, :<span class="ruby-identifier">path</span> =<span class="ruby-operator">&gt;</span> <span class="ruby-string">'/temp/profile'</span>
 <span class="ruby-keyword">end</span>
 </pre>
 
@@ -397,7 +394,7 @@ href="http://github.com/ruby-prof/ruby-prof/tree/master/examples/call_stack.html
 <p>Another good example: [<a
 href="http://twitpic.com/28z94a">twitpic.com/28z94a</a>]</p>
 
-<p>Finally, there&#39;s a so called MultiPrinter which can generate several
+<p>Finally, there’s a so called MultiPrinter which can generate several
 reports in one profiling run. See <a
 href="http://github.com/ruby-prof/ruby-prof/tree/master/examples/multi.stack.html">examples/multi.stack.html</a>.</p>
 
@@ -421,7 +418,7 @@ call graph report in text format</p>
 Creates a call graph report in HTML (separate files per thread)</p>
 </li><li>
 <p><a href="RubyProf/DotPrinter.html">RubyProf::DotPrinter</a> - Creates a
-call graph report in GraphViz&#39;s DOT format which can be converted to an
+call graph report in GraphViz's DOT format which can be converted to an
 image</p>
 </li><li>
 <p><a href="RubyProf/CallTreePrinter.html">RubyProf::CallTreePrinter</a> -
@@ -491,8 +488,8 @@ significant CPU or disk time during a profiling run then the reported
 results will be too large.</p>
 
 <p>CPU time uses the CPU clock counter to measure time.  The returned values
-are dependent on the correctly setting the CPU&#39;s frequency. This mode
-is only supported on Pentium or PowerPC platforms (linux only).</p>
+are dependent on the correctly setting the CPU’s frequency. This mode is
+only supported on Pentium or PowerPC platforms (linux only).</p>
 
 <p>Object allocation reports show how many objects each method in a program
 allocates.  This support was added by Sylvain Joyeux and requires a patched
@@ -504,16 +501,16 @@ This support was added by Alexander Dymo and requires a patched Ruby
 interpreter.  For more information, see: <a
 href="http://rubyforge.org/tracker/index.php?func=detail&aid=17676&group_id=1814&atid=7062">rubyforge.org/tracker/index.php?func=detail&aid=17676&group_id=1814&atid=7062</a></p>
 
-<p>Garbage collection runs report how many times Ruby&#39;s garbage collector
-is invoked during a profiling session.  This support was added by Jeremy
+<p>Garbage collection runs report how many times Ruby’s garbage collector is
+invoked during a profiling session.  This support was added by Jeremy
 Kemper and requires a patched Ruby interpreter.  For more information, see:
 <a
 href="http://rubyforge.org/tracker/index.php?func=detail&aid=17676&group_id=1814&atid=7062">rubyforge.org/tracker/index.php?func=detail&aid=17676&group_id=1814&atid=7062</a></p>
 
-<p>Garbage collection time reports how much time is spent in Ruby&#39;s
-garbage collector during a profiling session.  This support was added by
-Jeremy Kemper and requires a patched Ruby interpreter.  For more
-information, see: <a
+<p>Garbage collection time reports how much time is spent in Ruby’s garbage
+collector during a profiling session.  This support was added by Jeremy
+Kemper and requires a patched Ruby interpreter.  For more information, see:
+<a
 href="http://rubyforge.org/tracker/index.php?func=detail&aid=17676&group_id=1814&atid=7062">rubyforge.org/tracker/index.php?func=detail&aid=17676&group_id=1814&atid=7062</a></p>
 
 <p>To set the measurement:</p>
@@ -580,7 +577,7 @@ profiling run and is otherwise quiescent.</p>
 
 <p>On both platforms, cpu time is measured using the RDTSC assembly function
 provided by the Pentium and PowerPC platforms. CPU time is dependent on the
-cpu&#39;s frequency.  On Linux, ruby-prof attempts to read this value from
+cpu’s frequency.  On Linux, ruby-prof attempts to read this value from
 “/proc/cpuinfo.”  On Windows, you must manually specify the clock
 frequency.  This can be done using the RUBY_PROF_CPU_FREQUENCY environment
 variable:</p>
@@ -597,18 +594,18 @@ variable:</p>
 context switches in 1.8.  As a result, the timings ruby-prof reports for
 each thread may be slightly inaccurate.  In particular, this will happen
 for newly spawned threads that go to sleep immediately (their first call).
-For instance, if you use Ruby&#39;s timeout library to wait for 2 seconds,
-the 2 seconds will be assigned to the foreground thread and not the newly
+For instance, if you use Ruby’s timeout library to wait for 2 seconds, the
+2 seconds will be assigned to the foreground thread and not the newly
 created background thread.  These errors can largely be avoided if the
 background thread performs any operation before going to sleep.</p>
 
 <h2 id="label-Performance">Performance<span><a href="#label-Performance">&para;</a> <a href="#documentation">&uarr;</a></span></h2>
 
-<p>Significant effort has been put into reducing ruby-prof&#39;s overhead as
-much as possible.  Our tests show that the overhead associated with
-profiling code varies considerably with the code being profiled.  Most
-programs will run approximately twice as slow while highly recursive
-programs (like the fibonacci series test) will run three times slower.</p>
+<p>Significant effort has been put into reducing ruby-prof’s overhead as much
+as possible.  Our tests show that the overhead associated with profiling
+code varies considerably with the code being profiled.  Most programs will
+run approximately twice as slow while highly recursive programs (like the
+fibonacci series test) will run three times slower.</p>
 
 <h2 id="label-License">License<span><a href="#label-License">&para;</a> <a href="#documentation">&uarr;</a></span></h2>
 

data/doc/Rack/RubyProf.html

@@ -138,10 +138,10 @@
   <span class="ruby-ivar">@options</span> = <span class="ruby-identifier">options</span>
   <span class="ruby-ivar">@options</span>[<span class="ruby-value">:min_percent</span>] <span class="ruby-operator">||=</span> <span class="ruby-value">1</span>
   <span class="ruby-ivar">@tmpdir</span> = <span class="ruby-identifier">options</span>[<span class="ruby-value">:path</span>] <span class="ruby-operator">||</span> <span class="ruby-constant">Dir</span>.<span class="ruby-identifier">tmpdir</span>
-  <span class="ruby-ivar">@printer_klasses</span> = <span class="ruby-ivar">@options</span>[<span class="ruby-value">:printers</span>]  <span class="ruby-operator">||</span> {<span class="ruby-operator">::</span><span class="ruby-constant">RubyProf</span><span class="ruby-operator">::</span><span class="ruby-constant">FlatPrinter</span> =<span class="ruby-operator">&gt;</span> <span class="ruby-string">&#39;flat.txt&#39;</span>,
-                                              <span class="ruby-operator">::</span><span class="ruby-constant">RubyProf</span><span class="ruby-operator">::</span><span class="ruby-constant">GraphPrinter</span> =<span class="ruby-operator">&gt;</span> <span class="ruby-string">&#39;graph.txt&#39;</span>,
-                                              <span class="ruby-operator">::</span><span class="ruby-constant">RubyProf</span><span class="ruby-operator">::</span><span class="ruby-constant">GraphHtmlPrinter</span> =<span class="ruby-operator">&gt;</span> <span class="ruby-string">&#39;graph.html&#39;</span>,
-                                              <span class="ruby-operator">::</span><span class="ruby-constant">RubyProf</span><span class="ruby-operator">::</span><span class="ruby-constant">CallStackPrinter</span> =<span class="ruby-operator">&gt;</span> <span class="ruby-string">&#39;call_stack.html&#39;</span>}
+  <span class="ruby-ivar">@printer_klasses</span> = <span class="ruby-ivar">@options</span>[<span class="ruby-value">:printers</span>]  <span class="ruby-operator">||</span> {<span class="ruby-operator">::</span><span class="ruby-constant">RubyProf</span><span class="ruby-operator">::</span><span class="ruby-constant">FlatPrinter</span> =<span class="ruby-operator">&gt;</span> <span class="ruby-string">'flat.txt'</span>,
+                                              <span class="ruby-operator">::</span><span class="ruby-constant">RubyProf</span><span class="ruby-operator">::</span><span class="ruby-constant">GraphPrinter</span> =<span class="ruby-operator">&gt;</span> <span class="ruby-string">'graph.txt'</span>,
+                                              <span class="ruby-operator">::</span><span class="ruby-constant">RubyProf</span><span class="ruby-operator">::</span><span class="ruby-constant">GraphHtmlPrinter</span> =<span class="ruby-operator">&gt;</span> <span class="ruby-string">'graph.html'</span>,
+                                              <span class="ruby-operator">::</span><span class="ruby-constant">RubyProf</span><span class="ruby-operator">::</span><span class="ruby-constant">CallStackPrinter</span> =<span class="ruby-operator">&gt;</span> <span class="ruby-string">'call_stack.html'</span>}
 
   <span class="ruby-ivar">@skip_paths</span> = <span class="ruby-identifier">options</span>[<span class="ruby-value">:skip_paths</span>] <span class="ruby-operator">||</span> [<span class="ruby-regexp">%r{^/assets}</span>, <span class="ruby-regexp">%r{\.css$}</span>, <span class="ruby-regexp">%r{\.js$}</span>, <span class="ruby-regexp">%r{\.png$}</span>, <span class="ruby-regexp">%r{\.jpeg$}</span>, <span class="ruby-regexp">%r{\.jpg$}</span>, <span class="ruby-regexp">%r{\.gif$}</span>]
 <span class="ruby-keyword">end</span></pre>
@@ -194,7 +194,7 @@
       <span class="ruby-identifier">result</span> = <span class="ruby-ivar">@app</span>.<span class="ruby-identifier">call</span>(<span class="ruby-identifier">env</span>)
     <span class="ruby-keyword">end</span>
 
-    <span class="ruby-identifier">path</span> = <span class="ruby-identifier">request</span>.<span class="ruby-identifier">path</span>.<span class="ruby-identifier">gsub</span>(<span class="ruby-string">&#39;/&#39;</span>, <span class="ruby-string">&#39;-&#39;</span>)
+    <span class="ruby-identifier">path</span> = <span class="ruby-identifier">request</span>.<span class="ruby-identifier">path</span>.<span class="ruby-identifier">gsub</span>(<span class="ruby-string">'/'</span>, <span class="ruby-string">'-'</span>)
     <span class="ruby-identifier">path</span>.<span class="ruby-identifier">slice!</span>(<span class="ruby-value">0</span>)
 
     <span class="ruby-identifier">print</span>(<span class="ruby-identifier">data</span>, <span class="ruby-identifier">path</span>)
@@ -235,7 +235,7 @@
   <span class="ruby-ivar">@printer_klasses</span>.<span class="ruby-identifier">each</span> <span class="ruby-keyword">do</span> <span class="ruby-operator">|</span><span class="ruby-identifier">printer_klass</span>, <span class="ruby-identifier">base_name</span><span class="ruby-operator">|</span>
     <span class="ruby-identifier">printer</span> = <span class="ruby-identifier">printer_klass</span>.<span class="ruby-identifier">new</span>(<span class="ruby-identifier">data</span>)
     <span class="ruby-identifier">file_name</span> = <span class="ruby-operator">::</span><span class="ruby-constant">File</span>.<span class="ruby-identifier">join</span>(<span class="ruby-ivar">@tmpdir</span>, <span class="ruby-node">&quot;#{path}-#{base_name}&quot;</span>)
-    <span class="ruby-operator">::</span><span class="ruby-constant">File</span>.<span class="ruby-identifier">open</span>(<span class="ruby-identifier">file_name</span>, <span class="ruby-string">&#39;wb&#39;</span>) <span class="ruby-keyword">do</span> <span class="ruby-operator">|</span><span class="ruby-identifier">file</span><span class="ruby-operator">|</span>
+    <span class="ruby-operator">::</span><span class="ruby-constant">File</span>.<span class="ruby-identifier">open</span>(<span class="ruby-identifier">file_name</span>, <span class="ruby-string">'wb'</span>) <span class="ruby-keyword">do</span> <span class="ruby-operator">|</span><span class="ruby-identifier">file</span><span class="ruby-operator">|</span>
       <span class="ruby-identifier">printer</span>.<span class="ruby-identifier">print</span>(<span class="ruby-identifier">file</span>, <span class="ruby-ivar">@options</span>)
     <span class="ruby-keyword">end</span>
   <span class="ruby-keyword">end</span>

data/doc/RubyProf/AbstractPrinter.html

@@ -476,7 +476,7 @@ options.</p>
                for it to be printed out in the report.
                Default value is 0.
 
-:print_file  - True or false. Specifies if a method&#39;s source
+:print_file  - True or false. Specifies if a method's source
                file should be printed.  Default value if false.
 
 :sort_method - Specifies method used for sorting method infos.

data/doc/RubyProf/CallInfo.html

@@ -166,7 +166,7 @@
             <pre><span class="ruby-comment"># File lib/ruby-prof/call_info.rb, line 25</span>
 <span class="ruby-keyword">def</span> <span class="ruby-identifier">call_sequence</span>
   <span class="ruby-ivar">@call_sequence</span> <span class="ruby-operator">||=</span> <span class="ruby-keyword">begin</span>
-    <span class="ruby-identifier">stack</span>.<span class="ruby-identifier">map</span> {<span class="ruby-operator">|</span><span class="ruby-identifier">method</span><span class="ruby-operator">|</span> <span class="ruby-identifier">method</span>.<span class="ruby-identifier">full_name</span>}.<span class="ruby-identifier">join</span>(<span class="ruby-string">&#39;-&gt;&#39;</span>)
+    <span class="ruby-identifier">stack</span>.<span class="ruby-identifier">map</span> {<span class="ruby-operator">|</span><span class="ruby-identifier">method</span><span class="ruby-operator">|</span> <span class="ruby-identifier">method</span>.<span class="ruby-identifier">full_name</span>}.<span class="ruby-identifier">join</span>(<span class="ruby-string">'-&gt;'</span>)
   <span class="ruby-keyword">end</span>
 <span class="ruby-keyword">end</span></pre>
           </div>
@@ -276,7 +276,7 @@ from both praent end self.</p>
         <div class="method-description">
           
           <p>find a specific call in list of children. returns nil if not found. note:
-there can&#39;t be more than one child with a given target method. in other
+there can’t be more than one child with a given target method. in other
 words: x.children.grep{|y|y.target==m}.size &lt;= 1 for all method infos m
 and call infos x</p>
           

data/doc/RubyProf/CallInfoPrinter.html

@@ -80,7 +80,7 @@
     
 <p>Prints out the call graph based on <a href="CallInfo.html">CallInfo</a>
 instances.  This is mainly for debugging purposes as it provides access
-into into RubyProf&#39;s internals.</p>
+into into RubyProf’s internals.</p>
 
   </section>