Hello, I have submitted an issue about internal errors arising from the use of file names such as "real.chpl" and "list.chpl" (I'm sorry to have taken time to do this...)
https://github.com/chapel-lang/chapel/issues/6189 Actually, when I tried Chapel for the first time about 2 years ago, the first program I made was exactly this "real.chpl" (to define a real variable and print it, just for practice). But that program did not compile with this internal error. At that time, because I did not know that a file name implicitly defines a module name, I could not guess the cause of the trouble and just stopped making practice at that time. After than, I re-started learning Chapel (v1.14) and, in the last month, I again hit a very similar case with a file name "list.chpl" (which might have some intereference with the internal List module (?) and list type). Though this issue can be easily avoided by just using different file names, my concern is that this might discourage a new user to keep learning further, particularly because there are several "work-in-progress" message both in the PDF manual and the Chapel web site (so the user might assume that it may be too early to try the compiler). So, to avoid such an unfortunate case, I would appreciate it if some more explicit error message is printed when a user file name or module name is problematic (e.g., by interference with internal routines). I believe this would make the chance of new users to stumble on such trivial cases in the initial learning step. # By the way, I feel it would be even better not to use a file name implicitly as module names (like Python), but rather always define a module explicitly in files (like namespace in C++ or module in Fortran). Because this requires only adding two lines on the header and footer of the file (with no entire indent assumed), I guess things may become more explicit and more robust, e.g., for change of file names. Thanks very much for reading a long message and taking your time... Best regards, Takeshi Yamamoto ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
