From: Robert Klemme <shortcutter@...>
Date: 2008-10-01T22:20:01+09:00
Subject: Re: "ensure" hiding actual error

2008/10/1 Nit Khair <sentinel.2001@gmx.com>:
> Robert Klemme wrote:
>
>> This sounds strange because syntax errors should be caught earlier -
>> unless they stem from an "require" or "load". Can you post a short
>> example that reproduces the error?
>
> Could you elaborate on that?

When Ruby interpreter loads a file it checks syntax (you can do
yourself with "ruby -c <script>").  If there is a syntax error that
will be shown before execution starts at all.  If you require a file
and there is a syntax error in that there you will see an exception
stemming from the 'require':

1. error in main, 2. error in required:

15:20:13 OPSC_Gold_bas_dev_R1.2.3$ ruby -e 'puts 111+; require
ARGV.shift' <(echo /)
-e:1: syntax error, unexpected ';'
puts 111+; require ARGV.shift
          ^
15:20:22 OPSC_Gold_bas_dev_R1.2.3$ ruby -e 'puts 111; require
ARGV.shift' <(echo /)
111
-e:1:in `require': /dev/fd/63.rb:1: unterminated string meets end of
file (SyntaxError)
/dev/fd/63.rb:1: syntax error, unexpected tSTRING_END, expecting
tSTRING_CONTENT or tREGEXP_END or tSTRING_DBEG or tSTRING_DVAR
        from -e:1
15:20:26 OPSC_Gold_bas_dev_R1.2.3$

Cheers

robert

-- 
remember.guy do |as, often| as.you_can - without end