Hi -
> However that does not mean that there is any agreement about the merit
> of having such operators... but I can see from this email that you are
> not trying to get into that right now. I'll just point out that it will
> be time to talk about it before you find yourself doing a significant
> amount of work related to it and if you are hoping/expecting that work
> be merged.
I was just putting it out there for discussion.
I guess what I'm saying is that I didn't view the original email
to even be about a language change so much as how to try out
changes in the parser. (There didn't seem to be any context
or rationale for the change). There's plenty of change I've
misunderstood though.
I just loaded the latest version of CentOS 7 on one of our compute servers
and while it has Bison 3.0.4, Flex is still stuck at 2.5.37. Looks like I
will have to compile that one manually and stick it is /usr/local. The Red
Hat SCL system conflicts with some of the other systems we have to run.
What utilities do you recommend and what versions thereof please?
Are you asking about flex and bison versions, or something else?
Two systems I frequently use for compiler development have
these versions of flex and bison:
flex 2.6.4, bison (GNU Bison) 2.7
flex 2.6.4, bison (GNU Bison) 3.5.1
Other than these, we have some dependencies listed here:
https://chapel-lang.org/docs/usingchapel/prereqs.html
and other than those it's obvious things like installing
git and your favorite editor.
Best,
-michael
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers
