I just want to point out in Todd's credit that he both admitted that he
doesn't know how to use github, and that he's finally looked into making
pull requests.
On Fri, Jan 17, 2020 at 1:21 AM Elizabeth Mattijsen wrote:
> > On 16 Jan 2020, at 21:13, ToddAndMargo via perl6-users <
> perl6-us...@pe
On 2020-01-17 00:12, Veesh Goldman wrote:
he's finally looked into making pull requests.
Do you have a link to the pull requests for
the documentation? I'd like to add some examples
to a few pages.
Hi Todd,
On Fri, 17 Jan 2020 04:06:10 -0800
Todd Chester via perl6-users wrote:
> On 2020-01-17 00:12, Veesh Goldman wrote:
> > he's finally looked into making pull requests.
>
> Do you have a link to the pull requests for
> the documentation? I'd like to add some examples
> to a few pages.
On Fri, Jan 17, 2020 at 06:06 Todd Chester via perl6-users <
perl6-us...@perl.org> wrote:
>
>
> On 2020-01-17 00:12, Veesh Goldman wrote:
> > he's finally looked into making pull requests.
>
> Do you have a link to the pull requests for
> the documentation? I'd like to add some examples
> to a fe
On 2020-01-17 06:15, Shlomi Fish wrote:
Hi Todd,
On Fri, 17 Jan 2020 04:06:10 -0800
Todd Chester via perl6-users wrote:
On 2020-01-17 00:12, Veesh Goldman wrote:
he's finally looked into making pull requests.
Do you have a link to the pull requests for
the documentation? I'd like to add s
On 2020-01-17 06:58, Tom Browder wrote:
On Fri, Jan 17, 2020 at 06:06 Todd Chester via perl6-users
mailto:perl6-us...@perl.org>> wrote:
On 2020-01-17 00:12, Veesh Goldman wrote:
> he's finally looked into making pull requests.
Do you have a link to the pull requests for
the
On 2020-01-17 11:43, ToddAndMargo via perl6-users wrote:
On 2020-01-17 06:58, Tom Browder wrote:
On Fri, Jan 17, 2020 at 06:06 Todd Chester via perl6-users
mailto:perl6-us...@perl.org>> wrote:
On 2020-01-17 00:12, Veesh Goldman wrote:
> he's finally looked into making pull requests.
On Fri, Jan 17, 2020 at 1:44 PM ToddAndMargo via perl6-users
wrote:
...
> Was this what you were referring to?
>
> https://github.com/Raku/doc/blob/master/CONTRIBUTING.md
No, check this link:
https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request
-
On 2020-01-17 11:55, Tom Browder wrote:
On Fri, Jan 17, 2020 at 1:44 PM ToddAndMargo via perl6-users
wrote:
...
Was this what you were referring to?
https://github.com/Raku/doc/blob/master/CONTRIBUTING.md
No, check this link:
https://help.github.com/en/github/collaborating-with-issues-and-p
If the issue is that you aren’t comfortable enough with Git¹, I assume as
part of the basic toolkit of a sysadmin you know how to generate a unified
diff patchfile (with `diff -ruN` or equivalent)?
If so, if you generate one and upload it attached to a GitHub issue, we can
figure out how to turn i
On 2020-01-17 12:20, Trey Harris wrote:
If the issue is that you aren’t comfortable enough with Git¹, I assume
as part of the basic toolkit of a sysadmin you know how to generate a
unified diff patchfile (with `diff -ruN` or equivalent)?
If so, if you generate one and upload it attached to a G
A 17 de janeiro de 2020 21:44:00 CET, ToddAndMargo via perl6-users
escreveu:
>On 2020-01-17 12:20, Trey Harris wrote:
>> If the issue is that you aren’t comfortable enough with Git¹, I assume
>> as part of the basic toolkit of a sysadmin you know how to generate a
>> unified diff patchfile (wit
On Fri, Jan 17, 2020 at 15:44 ToddAndMargo via perl6-users <
perl6-us...@perl.org> wrote:
> On 2020-01-17 12:20, Trey Harris wrote:
> > If the issue is that you aren’t comfortable enough with Git¹, I assume
> > as part of the basic toolkit of a sysadmin you know how to generate a
> > unified diff
Hi JJ,
Please be my hero.
I won't call you any goofy names out of
affection and friendship, as others will get
their nickers in a twist.
This is from a previous conversation we had concerning
the mistake in
https://docs.raku.org/language/nativecall#index-entry-nativecall
my $string = "FOO
On 2020-01-17 13:47, Trey Harris wrote:
On Fri, Jan 17, 2020 at 15:44 ToddAndMargo via perl6-users
mailto:perl6-us...@perl.org>> wrote:
On 2020-01-17 12:20, Trey Harris wrote:
> If the issue is that you aren’t comfortable enough with Git¹, I
assume
> as part of the basic toolk
Todd (and others),
So a few things.
1)
JJ's example worked by chance. (sorry JJ).
It worked because it just so happens that either his OS zero filled the
block he was allocated by the allocator
or because he didn't reuse the block that was given to him initially by the
allocator.
2)
If you assu
On Fri, Jan 17, 2020 at 17:35 ToddAndMargo via perl6-users <
perl6-us...@perl.org> wrote:
> Hi Trey,
>
> I wanted to add an example to
>
> https://docs.raku.org/routine/+$CIRCUMFLEX_ACCENT
>
> Do I Git the entire documentation project to do so?
> Can I jsut Git that page? If so, where do I find
>
On 2020-01-17 15:34, Paul Procacci wrote:
Todd (and others),
So a few things.
1)
JJ's example worked by chance. (sorry JJ).
It worked because it just so happens that either his OS zero filled the
block he was allocated by the allocator
or because he didn't reuse the block that was given to hi
On 2020-01-17 16:02, Trey Harris wrote:
On Fri, Jan 17, 2020 at 17:35 ToddAndMargo via perl6-users
mailto:perl6-us...@perl.org>> wrote:
Hi Trey,
I wanted to add an example to
https://docs.raku.org/routine/+$CIRCUMFLEX_ACCENT
Do I Git the entire documentation project to do so?
>> Take a peak at N1570, 5.2.1p2, 7.1.1 and 6.7.9,p14.
>> leaving off the nul is not a valid way of presenting a
>> string to a C function.
Here's the rub though Todd. Who is saying it's a string that is being
passed? (Hint: You are)
If the intention is to pass 3 bytes "FOO" starting at a given
For anyone following along that is not familiar with
C, a BYTE in C is called a Char in C. (Causes
some interesting conversations when UTF16 gets involved.)
On 2020-01-17 17:03, Paul Procacci wrote:
>> Take a peak at N1570, 5.2.1p2, 7.1.1 and 6.7.9,p14.
>> leaving off the nul is not a valid
>> For anyone following along that is not familiar with
>> C, a BYTE in C is called a Char in C. (Causes
>> some interesting conversations when UTF16 gets involved.)
I don't want to make this about C, but to clarify there's no type called
"BYTE" in the C language.
If BYTE is defined it's system d
Hi All,
https://docs.raku.org/routine/+$CIRCUMFLEX_ACCENT
(Operators) infix +^§
multi sub infix:<+^>($a, $b --> Int:D)
Integer bitwise XOR operator: Coerces both arguments to Int and does a
bitwise XOR (exclusive OR) operation.
$ p6 'my uint8 $x=0b0101_0111; my uint8 $y = 0b_; my u
As you say, +^ is an infix operator. Why are you trying to use it as a
function?
Try $z = $x +^ $y.
On Sat, 18 Jan 2020 at 15:03, ToddAndMargo via perl6-users <
perl6-us...@perl.org> wrote:
> Hi All,
>
> https://docs.raku.org/routine/+$CIRCUMFLEX_ACCENT
>
> (Operators) infix +^§
>
> multi sub in
multi sub infix:<+^>($a, $b --> Int:D)
_infix_ here is the keyword for you.
my uint8 $z = $x +^ $y;
On Fri, Jan 17, 2020 at 11:03 PM ToddAndMargo via perl6-users <
perl6-us...@perl.org> wrote:
> Hi All,
>
> https://docs.raku.org/routine/+$CIRCUMFLEX_ACCENT
>
> (Operators) infix +^§
>
> multi s
On Sat, 18 Jan 2020 at 15:03, ToddAndMargo via perl6-users
mailto:perl6-us...@perl.org>> wrote:
Hi All,
https://docs.raku.org/routine/+$CIRCUMFLEX_ACCENT
(Operators) infix +^§
multi sub infix:<+^>($a, $b --> Int:D)
Integer bitwise XOR operator: Coerces both arguments to I
On Fri, Jan 17, 2020 at 11:03 PM ToddAndMargo via perl6-users
mailto:perl6-us...@perl.org>> wrote:
Hi All,
https://docs.raku.org/routine/+$CIRCUMFLEX_ACCENT
(Operators) infix +^§
multi sub infix:<+^>($a, $b --> Int:D)
Integer bitwise XOR operator: Coerces both arguments t
In Raku, all operators are just functions with a funny syntax, but if you
want to use it as a function, you need the full name.
infix:<+^>($x, $y) would probably work just as well.
And where is the '$' before the z?
On Sat, 18 Jan 2020 at 15:45, ToddAndMargo via perl6-users <
perl6-us...@perl.or
On 2020-01-17 20:43, ToddAndMargo via perl6-users wrote:
On Sat, 18 Jan 2020 at 15:03, ToddAndMargo via perl6-users
mailto:perl6-us...@perl.org>> wrote:
Hi All,
https://docs.raku.org/routine/+$CIRCUMFLEX_ACCENT
(Operators) infix +^§
multi sub infix:<+^>($a, $b --> Int:D)
On 2020-01-17 20:49, Kevin Pye wrote:
n Raku, all operators are just functions with a funny syntax, but if you
want to use it as a function, you need the full name.
infix:<+^>($x, $y) would probably work just as well.
$z = +^($x, $y)
no work so well.
$ p6 'my uint8 $x=0b0101_0111; my uint8
On 2020-01-17 20:49, Kevin Pye wrote:
In Raku, all operators are just functions with a funny syntax
I like the way you wrote that. Your technical
writing just got some fan mail.
Apocalypse 3:
"*operators are just funny* looking *function* calls"
On Sat, Jan 18, 2020 at 12:31 AM ToddAndMargo via perl6-users <
perl6-us...@perl.org> wrote:
> On 2020-01-17 20:49, Kevin Pye wrote:
> > In Raku, all operators are just functions with a funny syntax
>
> I like the way you wrote
On 2020-01-17 21:43, Paul Procacci wrote:
Apocalypse 3:
"/operators are just funny/ looking /function/ calls"
Chuckle!
On 2020-01-17 9:00 p.m., ToddAndMargo via perl6-users wrote:
Still don't know what they used the word "sub"
The term "sub" is short for "subroutine", and declaring routines that way is
part of the Perl legacy that lasted into Raku. -- Darren Duncan
34 matches
Mail list logo
