Problems with Require

[seabird20]

All, I have recently downloaded Ruby In Steel - looks like v1.4. I am running inside VisualStudio 2005 Pro.

There are a couple of weirdnesses in the testing area (and possibly elsewhere too, but this is where I have seen them).

The require statements inside test_helper.rb are:

require File.expand_path(File.dirname(__FILE__) + "/../config/environment")
require 'test_help'

The first one complains that require has to take a litreral constant
The second one complains that it can't "require test_help at line 3"

Two questions:

Is this serious? If so, any ideas what to do about it?

Thanks

Chris

[Dermot]

No, it's not serious.

The IntelliSense system needs to know about required files because they contain code which may be useful. However, IS only processes require files that it can open.

So things like

require 'x.rb'

are easy to deal with and work fine. Anything else causes trouble.

The second one should be openable by IS, so there's something  wrong in the paths that it searches. The search paths are typically the current directory (and sub directories) and most of the Ruby file directories, so it looks like 'test_help' isn't in one of the search paths.

But the warning messages are only that - warnings that IS can't find them.

Dermot

[seabird20]

Thanks. That was only an example, there are other places, so somehow I must have the paths messed up. Any hints on knowing how to discover what the path is (presumably the appropriate system variable, but I can't remember which one and I don't have pickaxe handy!) and then second if there is something missing how to get it included.

Thanks

C

[Dermot]

It's

$:

There isn't a simple way to get the paths used in parsing, unfortunately.

Dermot

[flayer]

I had a problem with require in which the target file was sited in the same directory as the source file but the target file contained the following line:

alias ar_unformatted_block= :unformatted_block=

RiS seems unable to parse ":unformatted_block=", indicating this with a red squiggle under the "=" and the associated tool tip text message "unexpected token: '='".

[Dermot]

That looks like problem with the parser. I've added a bug to our tracking system.

Dermot