Re^8: It has been suggested to rename Perl 6 in order to boost its marketing potential. Which name would you prefer?

> The use of interpreter-based threads in perl is officially discouraged

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
[download]

Comment on Re^8: It has been suggested to rename Perl 6 in order to boost its marketing potential. Which name would you prefer? Download Code

Replies are listed 'Best First'.
Re^9: It has been suggested to rename Perl 6 in order to boost its marketing potential. Which name would you prefer? by liz (Monsignor) on Jul 16, 2018 at 12:28 UTC
Indeed, it is not so easy. Still I think there would be a good chance of salvaging the threads API by ditching the current Perl 5 ithreads implementation and spending (I think a relative small effort) to make forks core and rename it to "threads". And you wouldn't even have to build your perl with `-Dmultiplicity`, because forks supports this out of the box.	[reply] [d/l]
Re^10: It has been suggested to rename Perl 6 in order to boost its marketing potential. Which name would you prefer? by Anonymous Monk on Jul 17, 2018 at 06:40 UTC
Still I think there would be a good chance of salvaging the threads API by ditching the current Perl 5 ithreads implementation and spending (I think a relative small effort) to make forks core and rename it to "threads" No. We dont need more fraud.	[reply]