Good suggestion, but before I was going to bother the RAKUDO people (who must be busy now with putting together the Perl 6.0.0 release) I first wanted to check if it was just me or whether anyone else here suffered the same.
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics
| [reply] |
(As subsequent posts on this thread have already suggested ...) “Go ahead and give them the heads-up.” Now that Win-10 is official, and (this variation of ...) Perl6 is the same, any error-message that is encountered in the field and suspected to be incorrect needs to be reported as soon as possible. It is entirely possible, likely, that the compatibility-test itself is in error ... and that the error is a trivial one. “D’oh!”
But also ... since the idea of having to deal with any sort of “separate VM” is a new concept in the Perl world, any user-feedback about the actual installation experience, and first-blush reactions any messages received along the way, are likely to be useful to someone at this point. Provide “as many details as possible” when you report your findings to them.
| |
| [reply] |