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
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:
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: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-users@perl.org>> wrote:
On 2020-01-17 00:12, Veesh Goldman wrote:
> he's finally looked into making pull
On 2020-01-17 06:58, Tom Browder wrote:
On Fri, Jan 17, 2020 at 06:06 Todd Chester via perl6-users
mailto:perl6-users@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 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
On Fri, Jan 17, 2020 at 06:06 Todd Chester via perl6-users <
perl6-users@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
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 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.
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 <
>
> On 16 Jan 2020, at 21:13, ToddAndMargo via perl6-users
> wrote:
> On 2020-01-16 12:09, Elizabeth Mattijsen wrote:
>>> On 16 Jan 2020, at 20:29, Darren Duncan wrote:
>>> On 2020-01-16 3:09 a.m., Elizabeth Mattijsen wrote:
I wonder if this is how you treat your family as well. If you do,
Trey,
I am wrong ALL THE TIME. I have to apologize all
the time too. I live with egg on my face constantly.
You get use to it.
When I am in the wrong, I will bend over five way to
Sunday to apologize.
If you decide to take offense where none is intended
and you have it explained to
On Thu, Jan 16, 2020 at 15:04 ToddAndMargo via perl6-users <
perl6-users@perl.org> wrote:
> On 2020-01-16 11:00, Trey Harris wrote:
> and your apparent misapprehension that
> merely explaining away a statement that some took offense to, without
> any outward sign of contrition, inoculates you
On 2020-01-16 12:09, Elizabeth Mattijsen wrote:
On 16 Jan 2020, at 20:29, Darren Duncan wrote:
On 2020-01-16 3:09 a.m., Elizabeth Mattijsen wrote:
I wonder if this is how you treat your family as well. If you do, then I feel
sorry for your family. And wouldn't be surprised if they abandoned
On 2020-01-16 12:09, ToddAndMargo via perl6-users wrote:
On 2020-01-16 11:29, Darren Duncan wrote:
On 2020-01-16 3:09 a.m., Elizabeth Mattijsen wrote:
I wonder if this is how you treat your family as well. If you do,
then I feel sorry for your family. And wouldn't be surprised if they
On 2020-01-16 11:29, Darren Duncan wrote:
On 2020-01-16 3:09 a.m., Elizabeth Mattijsen wrote:
I wonder if this is how you treat your family as well. If you do,
then I feel sorry for your family. And wouldn't be surprised if they
abandoned you.
That is unnecessarily harsh and uncalled for
> On 16 Jan 2020, at 20:29, Darren Duncan wrote:
> On 2020-01-16 3:09 a.m., Elizabeth Mattijsen wrote:
>> I wonder if this is how you treat your family as well. If you do, then I
>> feel sorry for your family. And wouldn't be surprised if they abandoned you.
> That is unnecessarily harsh and
On 2020-01-16 11:00, Trey Harris wrote:
On Thu, Jan 16, 2020 at 12:19 ToddAndMargo via perl6-users
mailto:perl6-users@perl.org>> wrote:
As far as the Dog remark, I have told you and others
ENDLESSLY what that meant. That you continue to
deliberately misrepresent me on this is a
On 2020-01-16 3:09 a.m., Elizabeth Mattijsen wrote:
I wonder if this is how you treat your family as well. If you do, then I feel
sorry for your family. And wouldn't be surprised if they abandoned you.
That is unnecessarily harsh and uncalled for Liz, the last sentence
particularly.
--
On 2020-01-16 9:22 a.m., ToddAndMargo via perl6-users wrote:
Since folks do not like the programming/math term
"carinal", it would be perfectly happy if the error
message was changed from:
This type cannot unbox to a native integer: P6opaque, Str
to
This type cannot unbox to a native unsigned
On Thu, Jan 16, 2020 at 12:19 ToddAndMargo via perl6-users <
perl6-users@perl.org> wrote:
> As far as the Dog remark, I have told you and others
> ENDLESSLY what that meant. That you continue to
> deliberately misrepresent me on this is a moral
> issue on your part.
The issue is not, now, just
On 2020-01-09 10:10, ToddAndMargo via perl6-users wrote:
Hi All,
A bug to report:
$ perl6 -v
This is Rakudo version 2019.07.1 built on MoarVM version 2019.07.1
implementing Perl 6.d.
$ p6 'my uint32 $c; $c = "ABC";'
This type cannot unbox to a native integer: P6opaque, Str
in block at -e
Hi Liz,
The Pull Request seems a much better route than the bug
reporter. I went to the bug reporter as I am familiar
with such from Fedora and others where you can ask
for enhancements, etc. on the bug reporter.
As far as the Dog remark, I have told you and others
ENDLESSLY what that meant.
> On 16 Jan 2020, at 02:24, ToddAndMargo via perl6-users
> wrote:
> Programming is only part of my business. I am a
> consultant to small business. I do EVERYTHING, although
> I draw the line at stringing wire. Fortunately, I have
> guys that will string wire for me.
Apparently you also draw
On 2020-01-15 17:32, Tillman Peng wrote:
I in fact like to read Todd's every post. Because of his active posting,
I know perl6 is there and still alive.
regards.
Thank you for that.
:-)
I in fact like to read Todd's every post. Because of his active posting,
I know perl6 is there and still alive.
regards.
on 2020/1/16 5:57, Richard Hainsworth wrote:
Todd,
Once again I find myself writing to you directly in response to a post
of yours and asking again that you be respectful
On 2020-01-15 16:59, Peter Scott wrote:
On 1/15/2020 2:39 PM, ToddAndMargo via perl6-users wrote:
On 2020-01-15 14:18, Elizabeth Mattijsen wrote:
Thank you Richard for this long and thoughtful answer.
I have already given up on Todd, I'm glad to see others haven't
(yet). What will follow is
On 2020-01-15 16:47, Tom Browder wrote:
On Wed, Jan 15, 2020 at 18:38 ToddAndMargo via perl6-users
mailto:perl6-users@perl.org>> wrote:
On 2020-01-15 15:50, Laurent Rosenfeld via perl6-users wrote:
> So, the way you behave with him is just nasty and evil. Please stop
> doing
On 1/15/2020 2:39 PM, ToddAndMargo via perl6-users wrote:
On 2020-01-15 14:18, Elizabeth Mattijsen wrote:
Thank you Richard for this long and thoughtful answer.
I have already given up on Todd, I'm glad to see others haven't
(yet). What will follow is probably a response that is either: a.
On 2020-01-15 15:36, Trey Harris wrote:
And there’s another example of exactly the sort of things Richard
brought up.
How about: “I feel like Richard has not liked me for a long time, and
that there’s nothing I can do about it. I feel like I could say almost
anything and he would find
On Wed, Jan 15, 2020 at 18:38 ToddAndMargo via perl6-users <
perl6-users@perl.org> wrote:
> On 2020-01-15 15:50, Laurent Rosenfeld via perl6-users wrote:
> > So, the way you behave with him is just nasty and evil. Please stop
> > doing that.
>
> That is in your own head.
Todd, why can't you
On 2020-01-15 15:50, Laurent Rosenfeld via perl6-users wrote:
So, the way you behave with him is just nasty and evil. Please stop
doing that.
That is in your own head.
The point is really not whether people like you or don't, and also not
about whether you like specific people or don't.
I don't know you (at least personally), you don't know me personally, and
nobody cares about whether I like you or whether you like me.
The whole point is about being polite,
On 2020-01-15 15:36, Trey Harris wrote:
artificially-hyperbolized reference to JJ helped anything after
previously calling him a dog.
To anyone still misunderstanding this. "Guard Dog" is
a figure of speech. It means he is over protective.
I DID NOT CALL HIM A DOG. And JJ knew this. I was
On Wed, Jan 15, 2020 at 17:39 ToddAndMargo via perl6-users <
perl6-users@perl.org> wrote:
> On 2020-01-15 14:18, Elizabeth Mattijsen wrote:
> > Thank you Richard for this long and thoughtful answer.
> >
> > I have already given up on Todd, I'm glad to see others haven't (yet).
> What will follow
On 2020-01-15 15:05, Laurent Rosenfeld via perl6-users wrote:
I join with Liz and Tom to thank you, Richard, for this long and
thoughtful answer.
Hi Laurent,
I can be long winded too. Wait, it is okay for
Richard, but not for me?
Anyway, I will eventually wear you down and
we will become
Richard,
Please put aside your personal distaste of me
when writing on this group.
Write me off line if you want to want to
vent.
-T
On 2020-01-15 14:25, Tom Browder wrote:
On Wed, Jan 15, 2020 at 4:19 PM Elizabeth Mattijsen wrote:
Thank you Richard for this long and thoughtful answer.
Amen, Liz!
-Tom (tbrowder)
With love and understanding, I will wear both you down
and we will become friends again.
On 2020-01-15 13:57, Richard Hainsworth wrote:
Todd,
Once again I find myself writing to you directly in response to a post
of yours and asking again that you be respectful to others in this
community. Striving for respect for everyone from everyone directly
benefits us all.
And disrespect
Todd,
You just did exactly what Liz said you would do by writing 'Richard has
not liked me for a long time'.
Do you not even re-read your own posts or have the self-awareness to
recognise it? Really?
Does it matter whether or not 'I like you'? This list is not some place
for social media
I join with Liz and Tom to thank you, Richard, for this long and thoughtful
answer.
Le mer. 15 janv. 2020 à 22:57, Richard Hainsworth
a écrit :
> Todd,
>
> Once again I find myself writing to you directly in response to a post
> of yours and asking again that you be respectful to others in
On 2020-01-15 14:18, Elizabeth Mattijsen wrote:
Thank you Richard for this long and thoughtful answer.
I have already given up on Todd, I'm glad to see others haven't (yet). What
will follow is probably a response that is either: a. everybody is against me,
b. the Raku community won't
On Wed, Jan 15, 2020 at 4:19 PM Elizabeth Mattijsen wrote:
>
> Thank you Richard for this long and thoughtful answer.
Amen, Liz!
-Tom (tbrowder)
Thank you Richard for this long and thoughtful answer.
I have already given up on Todd, I'm glad to see others haven't (yet). What
will follow is probably a response that is either: a. everybody is against me,
b. the Raku community won't listen, c. the various variations on those themes.
I
Todd,
Once again I find myself writing to you directly in response to a post
of yours and asking again that you be respectful to others in this
community. Striving for respect for everyone from everyone directly
benefits us all.
And disrespect harms you: your long emails defending your
On 2020-01-13 23:11, Darren Duncan wrote:
Yes, a uint32 CAN represent a cardinal, but it can ALSO represent an
ordinal or a nominal or various other things.
It would help me if you would show me some examples
of a uint would values were not whole nubmers
greater than or equal to zero
$_
On 2020-01-15 10:13, ToddAndMargo via perl6-users wrote:
Note that "*lpData" can be a little endian four byte
DWORD cardial or a UTF16 array of WORDS.
And the UTF array of WORDS is also little endian.
On 2020-01-14 01:13, JJ Merelo wrote:
Never miss a good chance to bash documentation...
Guilty as charged?
By the way, "C String" REQUIRES a nul at the end:
an error in the NativeCall documentation.
No, it does not. And even if it did, it should better go to the C, not
Raku,
El mar., 14 ene. 2020 1:24, ToddAndMargo via perl6-users <
perl6-users@perl.org> escribió:
> On 2020-01-13 15:16, Laurent Rosenfeld via perl6-users wrote:
> > Your own record over the last years shows that you very often don't
> > understand documentation (and I actually sometimes wonder whether
On 2020-01-13 22:56, Darren Duncan wrote:
Brad is saying what I've been saying, while a uint CAN represent a
cardinal number, one does NOT ALWAYS represent a cardinal number, so
saying this only IS a cardinal number is WRONG. -- Darren Duncan
Hi Darren,
You are mixing specific data
On 2020-01-12 11:32 p.m., ToddAndMargo via perl6-users wrote:
On 2020-01-12 20:03, Darren Duncan wrote:
A uint32 is NOT specifically a cardinal.
Since a uint32 ca not be negative or a fraction,
it is a cardinal. Other operating system do call
them cardinals, such as Modula2. Pascal, C++ (I
Brad is saying what I've been saying, while a uint CAN represent a cardinal
number, one does NOT ALWAYS represent a cardinal number, so saying this only IS
a cardinal number is WRONG. -- Darren Duncan
On 2020-01-13 12:56 p.m., Brad Gilbert wrote:
Ok looking into it, zero is inside of the set
On 2020-01-13 21:02, Aureliano Guedes wrote:
ToddAndMargo, this should handle any kind of columns separated data (or
any table). If some column (commonly separated with a constant character
as "\t", ";", "|", ) has different types (char, text, int, boolean,
...) in a single column, then
On 2020-01-13 21:02, Aureliano Guedes wrote:
ToddAndMargo, this should handle any kind of columns separated data (or
any table). If some column (commonly separated with a constant character
as "\t", ";", "|", ) has different types (char, text, int, boolean,
...) in a single column, then
ToddAndMargo, this should handle any kind of columns separated data (or any
table). If some column (commonly separated with a constant character as
"\t", ";", "|", ) has different types (char, text, int, boolean, ...)
in a single column, then it should be treated as a character, but if it has
>> what is the best strategy?
My general rule of thumb:
If you control the value then you can pick whatever data type that has the
largest number of bits to hold your largest value.[1]
If you don't control the value, stick with an Int (or Uint).
If you stick with Int you can later modify it to
On 2020-01-13 20:09, Aureliano Guedes wrote:
About the Raku typing, suppose I'll write a library to deal with data
frames/tables (as PDL - Perl(5) Data Language), something like
Pandas-Python or R.
After reading the file (csv; tsv ) I'd like that some routine
identifies the best type to
About the Raku typing, suppose I'll write a library to deal with data
frames/tables (as PDL - Perl(5) Data Language), something like
Pandas-Python or R.
After reading the file (csv; tsv ) I'd like that some routine
identifies the best type to fix each column (especially in cases like Unit,
On Mon, Jan 13, 2020 at 9:51 PM ToddAndMargo via perl6-users
mailto:perl6-users@perl.org>> wrote:
On 2020-01-13 18:46, ToddAndMargo via perl6-users wrote:
> On 2020-01-13 17:13, ToddAndMargo via perl6-users wrote:
>> And, no one is telling me percisely what the difference
>>
>> trying to find the constraints explanation in the documentation:
https://docs.raku.org/language/nativetypes
"Raku offers a set of *native* types with a fixed, and known,
representation in memory"
and
"However, these types do not necessarily have the size that is required by
the NativeCall
On 2020-01-13 18:46, ToddAndMargo via perl6-users wrote:
On 2020-01-13 17:13, ToddAndMargo via perl6-users wrote:
And, no one is telling me percisely what the difference
between UInt and uint is other than one is a subset of
Int and the other is a native type. They act exactly
the same.
Hi
On 2020-01-13 17:13, ToddAndMargo via perl6-users wrote:
And, no one is telling me percisely what the difference
between UInt and uint is other than one is a subset of
Int and the other is a native type. They act exactly
the same.
Hi All,
Off line, Paul told me what the difference is
between
On 2020-01-13 16:58, The Sidhekin wrote:
On Tue, Jan 14, 2020 at 1:25 AM ToddAndMargo via perl6-users
mailto:perl6-users@perl.org>> wrote:
On 2020-01-13 15:16, Laurent Rosenfeld via perl6-users wrote:
> The way you consistently mixed up uint and Uint in the last hours,
> despite
On Tue, Jan 14, 2020 at 1:25 AM ToddAndMargo via perl6-users <
perl6-users@perl.org> wrote:
> On 2020-01-13 15:16, Laurent Rosenfeld via perl6-users wrote:
> > The way you consistently mixed up uint and Uint in the last hours,
> > despite having been warned about this mistake, also shows a lack
On 2020-01-13 15:16, Laurent Rosenfeld via perl6-users wrote:
Your own record over the last years shows that you very often don't
understand documentation (and I actually sometimes wonder whether you're
even really interested in trying to understand it).
Actually, I go there a lot and I tear
> What makes you think I did not understand the documentation?
Your own record over the last years shows that you very often don't
understand documentation (and I actually sometimes wonder whether you're
even really interested in trying to understand it).
Your disdain for the documentation just
On 2020-01-13 14:22, The Sidhekin
wrote:
Your use of the term "uint" in reference
to "UInt" is what makes me think so.
uint and UInt are different types –
conceptually related, but with no type relation between them –
On Mon, Jan 13, 2020 at 10:46 PM ToddAndMargo via perl6-users <
perl6-users@perl.org> wrote:
> On 2020-01-13 12:43, The Sidhekin wrote:
>
> On Mon, Jan 13, 2020 at 8:51 PM ToddAndMargo via perl6-users <
> perl6-users@perl.org> wrote:
>
>> In https://docs.raku.org/type/UInt, a cardinal (uint)
>>
On 2020-01-13 12:43, The Sidhekin
wrote:
On Mon, Jan 13, 2020 at 8:51
PM ToddAndMargo via perl6-users
wrote:
On 2020-01-13 11:10,
On 2020-01-13 12:56, Brad Gilbert wrote:
Ok looking into it, zero is inside of the set of cardinal numbers.
It is still wrong to call a uint a cardinal number.
It's just wrong for a different reason.
Looking through various definitions, a cardinal number is a number which
represents a count
Ok looking into it, zero is inside of the set of cardinal numbers.
It is still wrong to call a uint a cardinal number.
It's just wrong for a different reason.
Looking through various definitions, a cardinal number is a number which
represents a count of sets.
So a uint could be used to
On Mon, Jan 13, 2020 at 8:51 PM ToddAndMargo via perl6-users <
perl6-users@perl.org> wrote:
> On 2020-01-13 11:10, ToddAndMargo via perl6-users wrote:
> >
> > https://docs.raku.org/type/UInt
> > Subset UInt
> > Unsigned integer (arbitrary-precision)
> > The UInt is defined as a subset
On 2020-01-13 11:10, ToddAndMargo via perl6-users wrote:
https://docs.raku.org/type/UInt
Subset UInt
Unsigned integer (arbitrary-precision)
The UInt is defined as a subset of Int:
my subset UInt of Int where {not .defined or $_ >= 0};
Consequently, it cannot be instantiated
On 2020-01-13 06:17, Brad Gilbert wrote:
According to the description you copied, a cardinal can never be zero.
any of the numbers
that express amount, as one, two, three, etc.
So it is more accurate to call it an integer.
Hi Brad,
Are you referring to "any of the numbers that
According to the description you copied, a cardinal can never be zero.
any of the numbers
that express amount, as one, two, three, etc.
So it is more accurate to call it an integer.
On Mon, Jan 13, 2020 at 1:32 AM ToddAndMargo via perl6-users <
perl6-users@perl.org> wrote:
> On
On 2020-01-12 23:20, WFB wrote:
Hi Todd,
For years, I have been playing around with programming stuff. I never
stumbled across the term "cardinal". Its obvious that I am not an native
English speaker and it does not hurt to learn new stuff. But, you makes
it harder to understand your
On 2020-01-12 20:03, Darren Duncan wrote:
On 2020-01-09 10:10 a.m., ToddAndMargo via perl6-users wrote:
A bug to report:
$ p6 'my uint32 $c; $c = "ABC";'
This type cannot unbox to a native integer: P6opaque, Str
in block at -e line 1
"uint32" is not an "integer". It is a cardinal. If
Hi Todd,
For years, I have been playing around with programming stuff. I never
stumbled across the term "cardinal". Its obvious that I am not an native
English speaker and it does not hurt to learn new stuff. But, you makes it
harder to understand your problems if you not use the common jargon.
On 2020-01-09 10:10 a.m., ToddAndMargo via perl6-users wrote:
A bug to report:
$ p6 'my uint32 $c; $c = "ABC";'
This type cannot unbox to a native integer: P6opaque, Str
in block at -e line 1
"uint32" is not an "integer". It is a cardinal. If
they really want to use the word "integer"
Here is one reason why you do these to to be
distinct from each other. In Win API calls to the
registry, REG_DWORDs are all cardinals, not
integers:
Here is a link to the graphicsthat did not come out:
https://social.msdn.microsoft.com/Forums/getfile/1525734
On 2020-01-12 09:18, Marcel Timmerman
wrote:
On 1/9/20 7:10 PM, ToddAndMargo via
perl6-users wrote:
'my
uint32 $c; $c = "ABC";'
The error shows that you cannot assign a string to an int (This
type cannot unbox to a
On 1/9/20 7:10 PM, ToddAndMargo via perl6-users wrote:
'my uint32 $c; $c = "ABC";'
The error shows that you cannot assign a string to an int (*This type
cannot unbox to a native integer: P6opaque, Str*)
You can do the following to get it right;
'p6 -e 'my uint32 $c; $c = 0xABC;''
82 matches
Mail list logo