General

Profile

BertramScharpf (Bertram Scharpf)

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 0 3 3

Activity

12/06/2013

06:38 AM Ruby master Bug #9167: Segmentation fault in cleanup
nobu (Nobuyoshi Nakada) wrote:
> Bertram, thank you for reporting this issue.
> Your contribution to Ruby is greatl...
BertramScharpf (Bertram Scharpf)

11/30/2013

02:20 AM Ruby master Feature #9123: Make Numeric#nonzero? behavior consistent with Numeric#zero?
alexeymuranov (Alexey Muranov) wrote:
> Please correct me if i am wrong, but i think that the most useful
> part of...
BertramScharpf (Bertram Scharpf)

11/28/2013

10:20 PM Ruby 1.8 Bug #9100: Just a typo in a #define that is not used anywhere
zzak (Zachary Scott) wrote:
> Is this bug only present in 1.8.7?
Definitely yes. If it were present in 1.9, I wou...
BertramScharpf (Bertram Scharpf)

11/27/2013

09:49 PM Ruby master Bug #9167 (Closed): Segmentation fault in cleanup
I don't know whether it is the interpreters fault or mine.
This is what I do:
- Subclassing StandardError in C
...
BertramScharpf (Bertram Scharpf)
07:22 PM Ruby 1.8 Bug #9100: Just a typo in a #define that is not used anywhere
Reminder: Not one single reaction in more than two weeks. BertramScharpf (Bertram Scharpf)
07:20 PM Ruby master Bug #9101: Reference to unset variable
Reminder: Not one single reaction in more than two weeks. BertramScharpf (Bertram Scharpf)

11/24/2013

01:31 AM Ruby master Feature #9123: Make Numeric#nonzero? behavior consistent with Numeric#zero?
alexeymuranov (Alexey Muranov) wrote:
> In my opinion, it is because code is intended mostly for reading, not for wr...
BertramScharpf (Bertram Scharpf)

11/21/2013

06:04 AM Ruby 1.8 Bug #9100: Just a typo in a #define that is not used anywhere
Reminder: Not one single reaction for ten days. BertramScharpf (Bertram Scharpf)
06:03 AM Ruby master Bug #9101: Reference to unset variable
Reminder: Not one single reaction for ten days. BertramScharpf (Bertram Scharpf)
06:00 AM Ruby master Feature #9123: Make Numeric#nonzero? behavior consistent with Numeric#zero?
> I'm not proposing a change to the semantics of Ruby; I'm proposing
> a fix to an inconsistency.
The opposite of...
BertramScharpf (Bertram Scharpf)

Also available in: Atom