Add local blocks to the BlockStmts walked during return path checking

The statements in a local block should be walked in isDefinedAllPaths in the
same way as for plain BlockStmts and do-while BlockStmts.  This gets rid of the
warning in users/ferguson/local-return.chpl, so remove that .future and .bad.
Merge branch 'master' of github.com:daviditen/chapel into localReturn

Conflicts:
	test/users/ferguson/local-return.bad
rebasing to get rid of whatever happened on the old one...
adding changes based upon review comments
Merge pull request #81 from daviditen/localReturn

Add local blocks to the BlockStmts walked during return path checking

The statements in a local block should be walked in isDefinedAllPaths in the
same way as for plain BlockStmts and do-while BlockStmts. This gets rid of the
warning in users/ferguson/local-return.chpl, so remove that .future and .bad.
Merge pull request #79 from tzakian/parallel-filesystems-redux

Adding parallel and distributed file system interface
Getting rid of qio_channel_filelength and instead adding qio_channel_get_channel_size
Added a bug future whereby the compiler crashes when a task intent's ref clause includes a reference to a field.

From the .future: instead an error should be generated.
That's because fields are not subject to forall intents.
Even fields of a record.

Also, my anticipated implementation of forall intents will likely hit
the same issue.

P.S. This should really be 8 distinct tests, to ensure that an error
is generated for each case. The param 'if' I am using does not guarantee
that - because the compiler may generate the error prior to resolution.
So ideally split this into 6 tests once the bug is fixed,
the add two for forall intents when those are working.
Merge pull request #85 from vasslitvinov/task-intents--field-in-ref-clause--bug

Added a bug future whereby the compiler crashes when a task intent's ref clause references a field.

From the .future: instead an error should be generated.
That's because fields are not subject to forall intents.
Even fields of a record.

Also, my anticipated implementation of forall intents will likely hit
the same issue.

P.S. This should really be 8 distinct tests, to ensure that an error
is generated for each case. The param 'if' I am using does not guarantee
that - because the compiler may generate the error prior to resolution.
So ideally split this into 6 tests once the bug is fixed,
the add two for forall intents when those are working.
Switching to use qio_channel_get_offset_unlocked and qio_channel_get_end_offset_unlocked
Add Vass's adlibs to Thomas's GitIntro.chpl
Merge pull request #86 from vasslitvinov/adlibs

Add Vass's adlibs to Thomas's GitIntro.chpl

"Vass has been here."
Added DIRNAME.skipif for some test dirs with custom 'sub_test'.
Merge pull request #87 from vasslitvinov/dir.skipifs-for-C-tests

Added DIRNAME.skipif for some test dirs with custom 'sub_test'.

The following directories:

  test/compflags/ferguson
  test/users/ferguson/bswap
  test/users/ferguson/sys/getenv
  test/regexp/ferguson/ctests
  test/io/ferguson/utf8cols
  test/io/ferguson/ctests
  test/functions/ferguson

(a) use custom 'sub_test', and
(b) need testing only under one configuration.

Since these 'sub_test' do not perform skipif checks, they were getting
tested under all configurations every night, which is excessive and
on occasion has created noise in our nightly emails.

So I am adding DIRNAME.skipif so for each DIRNAME in the above,
aiming at having those dirs be tested for the standard configuration only.
If there are other configurations that should be ruled out,
these skipifs should be extended.

As of this commit, the seven .skipif files are identical.
Merge pull request #84 from tzakian/readstring_fix

Fixing channel.readstring
This future was solved by my _defaultOf language feature, I believe due to the
change in the scopeResolve pass which caused ref variable fields to no longer be
default initialized, since the field will be assigned to at a later point.
Merge pull request #88 from lydia-duncan/fixFutureTest

Remove .future on passing future test

This future was solved by my _defaultOf language feature, I believe due to the change in the scopeResolve pass which caused ref variable fields to no longer be default initialized, since the field will be assigned to at a later point.
merging...