Hi, >> Another question, is it possible to split a module into multiple files? I >> recall seeing some notes about this implying that this isn't >> supported yet, but just wanted to make sure. > It is not at present within Chapel (one could of course run preprocessors > before passing files to Chapel). We've long planned to have an 'include' > statement (as in C or LaTeX), but were not able to implement it due to our > traditional use of bison. Recent changes in how we use bison are expected to > simplify the implementation of this feature but it's a ways out yet.
Okay. Just to make sure, does this mean that I can't have even nested modules in separate files? (Without resorting to the use of a preprocessor) Also I recall you telling about your intentions/wishes to change the way reindexing and rank changes (and some other operations?) are done, to make code in distributions simpler. Has this made any progress lately? The code of those functions seem so difficult that I have just commented them out in my distribution... ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
