It was just a stupid mistake on my part. I just didn't follow the logic,
and tried to access a variable out of scope. I should have reviewed the
code more. Thanks.


On Wed, Jun 11, 2014 at 3:08 PM, Jeremy Axelrod <axelrod.jeremy / gmail.com>
wrote:

> Can you explain the answer?
>
> Sent from my phone
>
> On Jun 11, 2014, at 11:58 AM, Justin Stanczak <rizenine / gmail.com> wrote:
>
> Oh crap. Just ignore me all together. I figured it out. Just one of those
> days. Not sure why I didn't put two and two together. Sorry.
>
>
> On Wed, Jun 11, 2014 at 2:49 PM, Justin Stanczak <rizenine / gmail.com>
> wrote:
>
>> No, scrap that. Did it again and it's working. Not sure why this is
>> having that issue.
>>
>>
>> On Wed, Jun 11, 2014 at 2:42 PM, Justin Stanczak <rizenine / gmail.com>
>> wrote:
>>
>>> I think this may be activesupport causing this. When I do true && false
>>> => false but with activesupport loaded I get nothing.
>>>
>>>
>>> On Wed, Jun 11, 2014 at 2:20 PM, Justin Stanczak <rizenine / gmail.com>
>>> wrote:
>>>
>>>> I'm using ruby-2.0.0-p353
>>>>
>>>> When I do this:
>>>>
>>>> def test_one?
>>>>    true
>>>> end
>>>>
>>>> def test_two?
>>>>    true
>>>> end
>>>>
>>>>
>>>> test_two? && test_one? => error
>>>>
>>>>
>>>> I get:  wrong number of arguments (0 for 2..3)
>>>>
>>>>
>>>> activesupport (4.1.1) is loaded.
>>>>
>>>>
>>>> Seems like it should not be an issue, or I'm missing something big.
>>>> Thanks.
>>>>
>>>>
>>>
>>
>