IronRuby r128 on Mono

Updated as usual.
http://sparcs.kaist.ac.kr/~tinuviel/download/IronRuby/patch-mono-r128

Tested against Mono 1.9.1 and Mono SVN r110339. Please report any
problems.
Patch is shrinking! I do appreciate Microsoft’s efforts.

Curious - why did you have to change the visibility of the NodeFlags
enum?

Thanks,
-John

One other question - why are you not using get_compile_path_list? This
gives us an extra level of protection in case someone leaves a file
behind in a directory that doesn’t need to be there (and this has
happened plenty of times in the past).

Thanks,
-John

2008/8/13 John L. (IRONRUBY) [email protected]:

One other question - why are you not using get_compile_path_list? This gives us an extra level of protection in case someone leaves a file behind in a directory that doesn’t need to be there (and this has happened plenty of times in the past).

Because *.csproj files are full of Windows paths, separated with
backslashes. Do I really need to explain that?!

Seems like it wouldn’t take too much work to canonicalize those paths,
right?

2008/8/13 John L. (IRONRUBY) [email protected]:

Curious - why did you have to change the visibility of the NodeFlags enum?

A bug of Mono C# compiler. I am trying to find a small repro.

On Thu, Aug 14, 2008 at 02:30:45AM +0900, Seo S. wrote:

2008/8/13 John L. (IRONRUBY) [email protected]:

Curious - why did you have to change the visibility of the NodeFlags enum?

A bug of Mono C# compiler. I am trying to find a small repro.

Did this get reported to Marek & co.?

2008/9/3 C.J. Adams-Collier [email protected]:

On Thu, Aug 14, 2008 at 02:30:45AM +0900, Seo S. wrote:

2008/8/13 John L. (IRONRUBY) [email protected]:

Curious - why did you have to change the visibility of the NodeFlags enum?

A bug of Mono C# compiler. I am trying to find a small repro.

Did this get reported to Marek & co.?

No, I failed to reduce the case.