Possible bug in ||= assignment 
Author Message
 Possible bug in ||= assignment

Hi,

Try the following:

  false ||= anObject
  true  ||= anObject
  nil   ||= anObject

=> Segmentation fault

  5        ||= anObject
  1.2      ||= anObject
  "string" ||= anObject
  [1,2]    ||= anObject

=> parse error

Happens in both 1.6.4 and 1.7.1.

Regards,

  Michael

--
Michael Neumann
merlin.zwo InfoDesign GmbH
http://www.*-*-*.com/



Wed, 21 Apr 2004 05:42:38 GMT  
 Possible bug in ||= assignment

Quote:

>   false ||= anObject
>   true  ||= anObject
>   nil   ||= anObject
> => Segmentation fault

also,

self     ||= anObject
__FILE__ ||= anObject
__LINE__ ||= anObject

and similarly all of those with &&=.

________________________________________________________________
Mathieu Bouchard                   http://hostname.2y.net/~matju



Wed, 21 Apr 2004 08:03:30 GMT  
 Possible bug in ||= assignment
Hi,

In message "[ruby-talk:24209] Possible bug in ||= assignment"

|Try the following:
|
|  false ||= anObject
|  true  ||= anObject
|  nil   ||= anObject
|
|=> Segmentation fault

They are bugs.

|  5        ||= anObject
|  1.2      ||= anObject
|  "string" ||= anObject
|  [1,2]    ||= anObject
|
|=> parse error

They are errors.  They are not assignable.
                                                        matz.



Wed, 21 Apr 2004 09:49:16 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. Possible fix for Bug 494589 - os.path.expandvars bug

2. Overriding assignment method-possible?

3. gawk 3.0.4 /= assignment...known bug?

4. Bug in non-blocking procedural assignment?

5. It seems bug in GNAT with overloading in assignment

6. elusive record assignment bug

7. Bug in Python large negative literal assignment?

8. Bugs from g77 - hex assignment and internal formats

9. BUGS, BUGS, BUGS, BUGS, C4 BUGS

10. No Assignment in Conditional/PROPOSAL: Assignment expression

11. Possible Catenation Bug In J 5.0 for the NeXT

12. 2 possible bugs

 

 
Powered by phpBB® Forum Software