On Mon, Oct 31, 2016 at 12:19 PM, Stephen J. Turnbull
wrote:
> Uh, as far as I can tell from that page, Perl has absolutely nothing
> to do with that. You enter the Unicode code point as hex, and if the
> font supports, you get the character. What Paul is arguing is that
> entering any character
Steven D'Aprano writes:
> I see that Perl is leading the way here, supporting a large number of
> Unicode symbols:
>
> https://docs.perl6.org/language/unicode_entry.html
In what sense is that "support"? What I see on that page is a lot of
advice for the kind of people who are already using
On Mon, Oct 31, 2016 at 12:02:54AM +1000, Nick Coghlan wrote:
> What this means is that there aren't likely to be many practical gains
> in using the "right" symbol for something, even when it's already
> defined in Unicode, as we expect the number of people learning that
> symbology *before* lear
On Sun, Oct 30, 2016 at 06:26:13AM -0700, David Mertz wrote:
> NaN's *usually* propagate. The NaN domain isn't actually closed under IEEE
> 754.
[...]
> >>> min(1, nan)
> 1
>
> The last one isn't really mandated by IEEE 754, and is weird when you
> consider `min(nan, 1)`.
Python's min() and ma
Paul Moore writes:
> They are on the keyboard. The £ sign is shift-3, the € sign uses the
> AltGr key (which is woefully underused on the standard UK keyboard
> driver - accented letters *should* be available using it :-()
OMG.
> Believe me, I've tried. But I should point out that I *don't*
Paul Moore writes:
> My point wasn't so much about dealing with the character set of
> Unicode, as it was about physical entry of non-native text. For
> example, on my (UK) keyboard, all of the printed keycaps are basically
> used.
How do you type the pound sign and the Euro sign? Are they o
Steven D'Aprano wrote:
> I cannot wait for the day that we can use non-ASCII operators. But I
> don't think that day has come: it is still too hard for many people
> (including me) to generate non-ASCII characters at the keyboard, and
> font support for some of the more useful ones are still incon
Hi all,
For those of you not aware, the Julia Programming Language [1] does
make extensive use of (mathematical) unicode symbols in its standard
library, even document a method of input [2] (hint tab completion).
They go even further by recognizing some characters (like \oplus) that
parse as opera
On 30 October 2016 at 14:51, Stephen J. Turnbull
wrote:
> Paul Moore writes:
>
> > My point wasn't so much about dealing with the character set of
> > Unicode, as it was about physical entry of non-native text. For
> > example, on my (UK) keyboard, all of the printed keycaps are basically
> >
On 2016-10-30 10:47 AM, Paul Moore wrote:
On 30 October 2016 at 14:43, wrote:
Just picking a nit, here, windows will happily let you do silly things like
hook 14 keyboards up and let you map all of emoji to them. Sadly, this
requires lua.
Off topic, I know, but how? I have a laptop with an
Paul Moore writes:
> My point wasn't so much about dealing with the character set of
> Unicode, as it was about physical entry of non-native text. For
> example, on my (UK) keyboard, all of the printed keycaps are basically
> used.
How do you type the pound sign and the Euro sign? Are they o
On 30 October 2016 at 14:43, wrote:
> Just picking a nit, here, windows will happily let you do silly things like
> hook 14 keyboards up and let you map all of emoji to them. Sadly, this
> requires lua.
Off topic, I know, but how? I have a laptop with an external and an
internal keyboard. Can
> -Original Message-
> From: Python-ideas [mailto:python-ideas-bounces+tritium-
> list=sdamon@python.org] On Behalf Of Paul Moore
> Sent: Sunday, October 30, 2016 8:22 AM
> To: Stephen J. Turnbull
> Cc: Python-Ideas
> Subject: Re: [Python-ideas] Non-ASCII in Python syntax? [was: Nul
On Mon, Oct 31, 2016 at 12:39 AM, Paul Moore wrote:
> It's certainly not difficult, in principle. I have (had, I lost it in
> an upgrade recently...) a little AutoHotkey program that interpreted
> Vim-style digraphs in any application that needed them. But my point
> was that we don't want to requ
On 30 October 2016 at 23:39, Paul Moore wrote:
> It's certainly not difficult, in principle. I have (had, I lost it in
> an upgrade recently...) a little AutoHotkey program that interpreted
> Vim-style digraphs in any application that needed them. But my point
> was that we don't want to require p
On 30 October 2016 at 12:31, Chris Angelico wrote:
> On Sun, Oct 30, 2016 at 11:22 PM, Paul Moore wrote:
>> In mentioning emoji, my main point was that "average computer users"
>> are more and more likely to want to use emoji in general applications
>> (emails, web applications, even documents) -
On Sat, Oct 29, 2016 at 11:44 PM, Stephan Hoyer wrote:
> I'm have more mixed fillings on testing for NaNs. NaNs propagate, so
> explicit testing is rarely needed. Also, in numerical computing we usually
> work with arrays of NaN, so operator.exists() and all this nice syntax
> would not be a subs
On Sun, Oct 30, 2016 at 11:22 PM, Paul Moore wrote:
> In mentioning emoji, my main point was that "average computer users"
> are more and more likely to want to use emoji in general applications
> (emails, web applications, even documents) - and if a sufficiently
> general solution for that proble
On 30 October 2016 at 07:00, Stephen J. Turnbull
wrote:
>> as I imagine Unicode characters would be for me. I really hope it
> > isn't...
>
> I think your imagination is running away with you. While I understand
> how costly it is for those over the age of 12 to develop new habits
> (I'm 58, and
Paul Moore writes:
> On 29 October 2016 at 18:19, Stephen J. Turnbull
> wrote:
> >> For better or worse, it may be emoji that drive that change ;-)
> >
> > I suspect that the 100 million or so Chinese, Japanese, Korean, and
> > Indian programmers who have had systems that have no trouble
>
20 matches
Mail list logo
