Re: [perl #132179] Don't put Mexico and Texas in opposition in Perl 6 jargon

Am 28.09.2017 um 15:44 schrieb brian d foy (via RT): > And, that's not bake any other geopolitical oppositions into the > language either. The Texas metaphor was a joke about that an American > stereotype and you shouldn't go further with it. Given that even good-natured humor occasionally gets

Re: [perl #132179] Don't put Mexico and Texas in opposition in Perl 6 jargon

Am 28.09.2017 um 15:44 schrieb brian d foy (via RT): And, that's not bake any other geopolitical oppositions into the language either. The Texas metaphor was a joke about that an American stereotype and you shouldn't go further with it. Given that even good-natured humor occasionally gets

Re: Your posting is a bit unfortunate

I'll respond privately to keep the noise of the list. Ask me to get cc'd. Regards, Jo

Re: [perl #131877] better error message for exit("hello")

Would it be possible to special case when someone passes a string to exit and give a better error message telling how to write that? Maybe the error message should indicate what types are allowed. Better yet, could exit accept a string? That would be equivalent to `print("hello");exit(0)`.

Re: [perl #131877] better error message for exit("hello")

> Would it be possible to special case when someone passes a string to > exit and give a better error message telling how to write that? Maybe the error message should indicate what types are allowed. > Better yet, could exit accept a string? That would be equivalent to

Re: Verifiable Releases/The Build System is Ridiculous

Am 29.07.2017 um 14:28 schrieb Timo Paulssen: Actually what they are refering to is that dyncall and libffi both require an executable stack. We can't get around that without making changes to libffi and dyncall, sadly. Ah okay, that was outside the bounds of my knowledge. And I agree it's

Re: Verifiable Releases/The Build System is Ridiculous

Am 29.07.2017 um 05:20 schrieb R0b0t1: Most issues I have seen that arise with submodules come from people trying to treat the submodule directory in a way that is different than other objects tracked by Git. If you treat it like a source file you're tracking most problems should disappear, at

Re: Verifiable Releases/The Build System is Ridiculous

Am 28.07.2017 um 04:35 schrieb R0b0t1: The earliest versions of the Rakudo Star build system started out by trying to use Git submodules to manage packages, but it quickly proved to be unwieldy and almost impossible to understand and maintain. Perhaps the submodule ecosystem has changed

Your posting is a bit unfortunate

Hi Robot, Understanding your points, correlating them to past decisions, calling up what the decisions actually were and their reasons, finding out which of these reasons were good and which were bad - that's already a pretty taxing task. Now if you start out with a dismissive attitude such

Re: [perl #131801] Stranded strings with combiners or ZWJ on borders break my NFG expectations ( (“\x[0305]a” x 2).chars.say )

The examples do not show forward-looking combiners. Not sure what's happening with the ZWJ - I dimly recall that Unicode says it is a misnomer and explicitly does not join arbitrary graphemes into characters, but I don't have the reference handy. Aleks-Daniel is showing that x 2 does not

Re: [perl #131757] Untodoed evil hack in Backtrace.pm

> See this: > https://github.com/rakudo/rakudo/blob/6c76ed0abe352316eb58283fa6ce6b8150fc6830/src/core/Backtrace.pm#L144 > > It goes like this: > > # now *that's* an evil hack > next if $file.ends-with('BOOTSTRAP.nqp') > || $file.ends-with('QRegex.nqp')

Re: [perl #131757] Untodoed evil hack in Backtrace.pm

Am 17.07.2017 um 09:32 schrieb Brandon Allbery: > On Mon, Jul 17, 2017 at 2:40 AM, Joachim Durchholz <j...@durchholz.org > <mailto:j...@durchholz.org>> wrote: > > I think the whole concept of defining what's "interesting" in > a backtrace

Re: [perl #131757] Untodoed evil hack in Backtrace.pm

Am 17.07.2017 um 11:34 schrieb jn...@jnthn.net via RT: > The code in question is implemented in NQP, which doesn't have a generalized > traits mechanism. Ahh, may bad, this being NQP files flew right by me and I didn't see it. I retract the traits idea - adding that just for this issue might be

Re: [perl #131757] Untodoed evil hack in Backtrace.pm

Am 17.07.2017 um 11:34 schrieb jn...@jnthn.net via RT: The code in question is implemented in NQP, which doesn't have a generalized traits mechanism. Ahh, may bad, this being NQP files flew right by me and I didn't see it. I retract the traits idea - adding that just for this issue might be

Re: [perl #131757] Untodoed evil hack in Backtrace.pm

Am 17.07.2017 um 09:32 schrieb Brandon Allbery: > On Mon, Jul 17, 2017 at 2:40 AM, Joachim Durchholz <j...@durchholz.org > <mailto:j...@durchholz.org>> wrote: > > I think the whole concept of defining what's "interesting" in > a backtrace by lo

Re: [perl #131757] Untodoed evil hack in Backtrace.pm

See this: https://github.com/rakudo/rakudo/blob/6c76ed0abe352316eb58283fa6ce6b8150fc6830/src/core/Backtrace.pm#L144 It goes like this: # now *that's* an evil hack next if $file.ends-with('BOOTSTRAP.nqp') || $file.ends-with('QRegex.nqp')

Re: [perl #126732] [RFC] Problem with superscripts when there is no number in front of it (³² == 9)

I do understand the operand-operator idea now, but I think that allowing the same symbol to be both operand and operator is a terrible idea. Feel free to disagree, I'm not going to argue that point. Otherwise: And since nobody is going to use that > > Yes! Exactly. You've put the nail in your

Re: [perl #126732] [RFC] Problem with superscripts when there is no number in front of it (³² == 9)

Am 08.06.2017 um 01:11 schrieb Zoffix Znet via RT: Quoting Joachim Durchholz <j...@durchholz.org>: Actually I'd like to *remove* a special case: That ² is to be interpreted as 2 But it's NOT a special case. You can use any character with No property as a numeric literal. That's. The.

Re: [perl #126732] [RFC] Problem with superscripts when there is no number in front of it (³² == 9)

Am 07.06.2017 um 23:09 schrieb Zoffix Znet via RT: What baffles me is we have several people calling for the ban on The Superscripts yet, no one appears appear to have any issues with ⅟², ၓ², ౸², ㆒², ̣², and ၒ² which are also perfectly valid sequences. I would have issues with these if I had

Re: [perl #126732] [RFC] Problem with superscripts when there is no number in front of it (³² == 9)

There's also the issue that undefined behaviour tends to become exploitable as part of a security hole. So I'm seconding Alekx-Daniel on this. Am 07.06.2017 um 17:48 schrieb Aleks-Daniel Jakimenko-Aleksejev via RT: (for example, because this kind of stuff makes the language look fragile).

Re: [perl #129843] [LTA] Indexing on a Str throws generic “out of range” message which is less than awesome (“hello”[2])

Am 08.05.2017 um 20:59 schrieb Brandon Allbery: On Mon, May 8, 2017 at 2:52 PM, Aleks-Daniel Jakimenko-Aleksejev via RT > wrote: Usually I'm against all perl5 error messages This is a Pythonism (and C and other such

Re: [perl #130914] [BUG] chr() aliases codepoint numbers mod 2**32

Am 19.03.2017 um 23:00 schrieb Christian Bartolomaeus via RT: Looking at https://en.wikipedia.org/wiki/Code_point and http://www.unicode.org/glossary/#code_point I understand that U+10 is indeed the maximum Unicode code point. Yes, that's the maximum value you can encode in four bytes with

Re: [perl #130900] [BUG] nul in pathname

On 02.03.2017 14:56, Brandon Allbery wrote: - any character disallowed by specific filesystems (consider CIFS) Wouldn't these characters be caught by the file system (whichever that is)? It would be pretty hard to do a reliable validation as soon as mounted filesystems come into play.

Re: [perl #130845] Some things that are less than 5 aren't

On 24.02.2017 13:03, Zoffix Znet via RT wrote: toolforger: p6: say Inf cmp Inf camelia: rakudo-moar 320c2f: OUTPUT: «Same␤» I.e. Inf compares equal to itself - is this intentional? Yes, and we didn't invent this concept. Heh. That's what you'd expect before reading IEEE. After understanding

Re: [perl #130845] Some things that are less than 5 aren't

Somewhat offtopic: toolforger: p6: say Inf cmp Inf camelia: rakudo-moar 320c2f: OUTPUT: «Same␤» I.e. Inf compares equal to itself - is this intentional?

Re: [perl #130660] make t/spec/foo/bar.t modifies the current installation

Am 29.01.2017 um 18:03 schrieb Zoffix Znet via RT: On Sun, 29 Jan 2017 08:46:28 -0800, j...@durchholz.org wrote: Can you explain? You're not running `make test` in that command. Oh. You mentioned `make test` in your first answer, so I was just assuming any differences would be irrelevant.

Re: [perl #130660] make t/spec/foo/bar.t modifies the current installation

Am 29.01.2017 um 14:58 schrieb Zoffix Znet via RT: On Sun, 29 Jan 2017 01:56:16 -0800, j...@durchholz.org wrote: My approach to solving this would be to have make test use perl-m resp. perl-j directly. OK. It already does so. Then it does not need to overwrite perl6. > As stated above,

Re: [perl #130660] make t/spec/foo/bar.t modifies the current installation

My approach to solving this would be to have make test use perl-m resp. perl-j directly. Adding another make target still leaves "make test" overwriting the perl6 file, which might be surprising if somebody has explicitly set up perl6 to mean (say) perl6-j.

Re: [perl #130542] AutoReply: \c[BELL] returns the U+0007 control code not U+1F514 BELL

Am 14.01.2017 um 11:29 schrieb Samantha McVey: See here for the commit that added some Alias Names to JVM: https://github.com/perl6/nqp/commit/0c249e7236a63325e6440df55a762a4378e6e63a Hopefully I have explained this well enough. I kinda expected this to be implemented in NQP and hence be

Re: [perl #130460] Can we relax indir's test on the target directory?

Am 03.01.2017 um 09:59 schrieb Elizabeth Mattijsen: On 3 Jan 2017, at 06:58, Joachim Durchholz <j...@durchholz.org> wrote: Yes, chdir is nasty because it's a global setting and you never know which of the functions you're calling might be changing the setting. indir solves all these

Re: [perl #130460] Can we relax indir's test on the target directory?

Am 03.01.2017 um 01:48 schrieb Zoffix Znet via RT: I see support from users for having the `indir` routine, Yes, chdir is nasty because it's a global setting and you never know which of the functions you're calling might be changing the setting. indir solves all these things. (Provided it

Re: [perl #130460] Can we relax indir's test on the target directory?

Am 02.01.2017 um 22:28 schrieb brian d foy: To me, the spirit of Perl has been "if that's what you want to do, here you go". I'd rather take on the burden of handling things if they blow up for things like this if it's a choice between that and not even getting to try it. Um, well, if it were

Re: [perl #130460] Can we relax indir's test on the target directory?

Am 30.12.2016 um 23:06 schrieb brian d foy (via RT): I don't know why it insists that the directory be writable, expecially when chdir itself is not as strict. I often change to a directory where I want to merely read files, so I'd like to see the test relaxed. If you go by Posix logic, indir

Re: [perl #129779] Concurrency worse than no concurrency

Am 11.10.2016 um 13:33 schrieb Steve Piner: On Tue, 04 Oct 2016 04:23:54 +1300, Joachim Durchholz via RT <perl6-bugs-follo...@perl.org> wrote: Am 03.10.2016 um 06:34 schrieb Zoffix Znet via RT: Seems the issue has more to do with running an empty loop, rather than performing

Re: [perl #129820] [NATIVECALL][LTA] callback returns useless error message

Am 06.10.2016 um 21:07 schrieb Brandon Allbery via RT: > Actually, now that I think about it, there is something that can be done; > not ideal, but the best we could do under the circumstances. Callbacks > should be given default exception handlers that at minimum output the > original exception

Re: [perl #129820] [NATIVECALL][LTA] callback returns useless error message

Am 06.10.2016 um 21:07 schrieb Brandon Allbery via RT: Actually, now that I think about it, there is something that can be done; not ideal, but the best we could do under the circumstances. Callbacks should be given default exception handlers that at minimum output the original exception (which

Re: [perl #129779] Concurrency worse than no concurrency

Am 03.10.2016 um 06:34 schrieb Zoffix Znet via RT: Seems the issue has more to do with running an empty loop, rather than performing a real computation. This is a run on a 4-core box. Attempting to parallelize an empty loop makes the execution 1 second slower: [...] But running actual

Re: Best way to get a PCRE6 on the JVM?

Am 29.09.2016 um 21:41 schrieb Patrick R. Michaud: On Thu, Sep 29, 2016 at 01:30:29PM +0200, Joachim Durchholz wrote: Can you tell me where the sources for the regex engine live? At the detailed-technical-spec level, I found S05, and I can find the NQP spec, but I don't know my way around

Re: Best way to get a PCRE6 on the JVM?

Am 28.09.2016 um 15:21 schrieb Will Coleda: To start with, there isn't a PCRE6. Good to know, then this is indeed the right list to discuss this. If you want, more generically, to be able to use Perl 6 Regular Expressions in Java, you can build a rakudo that runs (with reduced functionality)

Re: Best way to get a PCRE6 on the JVM?

Am 28.09.2016 um 15:46 schrieb Patrick R. Michaud: A simpler approach might be to build an NQP that runs on the JVM, Sounds reasonable, given NQP's position in the toolchain. Not sure what you mean with "build an NQP" - a compiler, a runtime, both, something else? > and find a way to call