General

Profile

andhapp (Anuj Dutta)

  • Login: andhapp
  • Email: anuj@andhapp.com
  • Registered on: 03/08/2010
  • Last sign in: 04/15/2014

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 1 6 7

Activity

02/20/2014

12:35 AM Ruby Bug #9534: bundle exec rake assets:precompile fails
Hey,
I noticed that you are on ruby 2.1.0p0. I could install ffi gem successfully for ruby-2.1.0 on Maverics. Just putting some information to help in debugging.
Regards
andhapp (Anuj Dutta)

01/03/2014

09:04 PM Ruby Bug #9358 (Closed): TracePoint's raise event should throw 'not supported by this event (RuntimeError)' on calling return_value
=begin
Hello,
In TracePoint class, if a particular introspection method is not supported then 'not supported by this event (RuntimeError)' is thrown.
=== Line event doesn't support raised_exception
TracePoint.trace(:line)...
andhapp (Anuj Dutta)
07:58 PM Ruby Bug #9357 (Closed): TracePoint's c_return traces return from call to 'trace'
=begin
Hello,
In TracePoint, trace on 'c_call' doesn't trace the call made to 'trace' method, where as trace on 'c_return' does, is this expected behaviour?
Here's the code I used to reproduce it:
=== Code (c_return)
clas...
andhapp (Anuj Dutta)
07:27 PM Ruby Feature #9355 (Open): Re: Rename method_id to method_name in TracePoint class
Hello,
I'd like to suggest renaming method_id (http://www.ruby-doc.org/core-2.1.0/TracePoint.html#method-i-method_id) to method_name in TracePoint class. There may be a particular reason for keeping it 'method_id', and I'd appreciate ...
andhapp (Anuj Dutta)

08/20/2013

06:18 PM Ruby Feature #8804: ONCE syntax
Hello,
Do you have any use-cases to share for the new syntax?
Thanks.
Regards
andhapp (Anuj Dutta)

05/22/2012

05:48 PM Ruby Bug #6477 (Rejected): BigDecimal to_i and to_int methods
Hello,
Why are there two methods, to_i and to_int, in BigDecimal when they are exactly same in terms of functionality. Here's the link to the docs:
http://www.ruby-doc.org/stdlib-1.9.3/libdoc/bigdecimal/rdoc/BigDecimal.html#method-...
andhapp (Anuj Dutta)

05/07/2012

02:45 AM Ruby Bug #6343: Improved Fiber documentation
Thanks, ok that makes sense. What should happen if someone does try and yield from a fiber that has been transferred control to from some other fiber? I will add it to RubySpec which is currently missing the spec for Fiber transfer. Than... andhapp (Anuj Dutta)

05/05/2012

08:11 AM Ruby Feature #2565: adding hooks for better tracing
Aaron,
Thanks. I had no idea about the licence.
Is your branch stable(ish) to try it out?
andhapp (Anuj Dutta)

05/03/2012

08:31 AM Ruby Bug #6395 (Closed): Fixed example for fiber transfer
The example for fiber transfer had incorrect output. Minor correction. andhapp (Anuj Dutta)
08:12 AM Ruby Bug #6343: Improved Fiber documentation
Hi,
Thanks ko1 for your comment. The example doesn't use Fiber#resume on fiber1. It uses Fiber.yield to return to the calling context. However, can you please explain how it should work? I mean, why do you think it's a bug?
Thanks.
andhapp (Anuj Dutta)

Also available in: Atom