On Aug 24, 2011, at 11:48 AM, Rob Biedenharn wrote:
>
> On Aug 23, 2011, at 5:18 PM, David Chelimsky wrote:
>
>>
>> On Aug 23, 2011, at 3:26 PM, Rob Biedenharn wrote:
>>
>>> On Aug 23, 2011, at 3:16 PM, David Chelimsky wrote:
>>>
On Aug 23, 2011, at 1:00 PM, Roger Pack wrote:
On Aug 23, 2011, at 5:18 PM, David Chelimsky wrote:
On Aug 23, 2011, at 3:26 PM, Rob Biedenharn wrote:
On Aug 23, 2011, at 3:16 PM, David Chelimsky wrote:
On Aug 23, 2011, at 1:00 PM, Roger Pack wrote:
This error message:
it 'should' do
proc { eval("a=")}.should raise_exception(/Synt
On Aug 23, 2011, at 3:26 PM, Rob Biedenharn wrote:
> On Aug 23, 2011, at 3:16 PM, David Chelimsky wrote:
>
>> On Aug 23, 2011, at 1:00 PM, Roger Pack wrote:
>>
>>> This error message:
>>>
>>>
>>> it 'should' do
>>>proc { eval("a=")}.should raise_exception(/SyntaxError/)
>>> end
>
> shoul
On Aug 23, 2011, at 3:16 PM, David Chelimsky wrote:
On Aug 23, 2011, at 1:00 PM, Roger Pack wrote:
This error message:
it 'should' do
proc { eval("a=")}.should raise_exception(/SyntaxError/)
end
shouldn't that be
raise_exception(SyntaxError)
that is, the exception class, not
On Aug 23, 2011, at 1:00 PM, Roger Pack wrote:
> This error message:
>
>
> it 'should' do
> proc { eval("a=")}.should raise_exception(/SyntaxError/)
> end
>
>
> expected Exception with message matching /SyntaxError/, got
> #
>
> Is a bit confusing, since it appears from the err
This error message:
it 'should' do
proc { eval("a=")}.should raise_exception(/SyntaxError/)
end
expected Exception with message matching /SyntaxError/, got
#
Is a bit confusing, since it appears from the error output that it
*does* match /SyntaxError/
Might be able to word
