@hcorion This is Neo2 (it states that itself) and it is an image for printing
and gluing on the keys. Therefore, there are multiple meta-key images to choose
from.
@Krux02 WTH kind of keyboard is that? Does it actually have 2 GNU keys, 2 BSD
keys and 2 Linux keys?
Ok, I give up.
Stop wasting everyone's time. Consider this thread closed.
> One key # is found only in UK and Ireland a far as I know.
Germany…
> Any keyboard, any standard, with numeric keypad, has + - * and /.
So moving your hand over to the numpad and back is faster than pressing two
keys?
> Just need people to think more open minded and understand that "this fea
> Just need people to think more open minded and understand that "this feature"
> adds much more than takes. To be true, it just adds.
As already stated, this is wrong. It takes away the `//` operator (that **you**
don't care about), and it introduces more divergent styles of writing code. And
One key # is found only in UK and Ireland a far as I know. Lucky guys, they are.
All arguments were done. Requested proof of importance presented. No need to
extend pro argumentation anymore. Just need people to think more open minded
and understand that "this feature" adds much more than takes.
> No attacks against anyone
You called people
> pythonic purists
which is obviously referring to people rather than the issue itself.
> I have no problems.
Your previous posts sounded differently.
> I want to help. Accept or deny.
Lacking commitment to discuss does not make your proposal loo
([https://s28.postimg.org/5ugjzoeql/tiobe-double-slashes.png](https://s28.postimg.org/5ugjzoeql/tiobe-double-slashes.png))
As for Ad Hominems, it's made when someone attacks another person, and not
his/her arguments. No attacks against anyone were made while argumenting. No Ad
Hominems were made
In my keyboard both '#' and '/' takes two keystrokes.
> 1\. Many keyboards does not have an one key access to "#", > as the "/" key,
> mine for instance, I usually need to look at alt-3 > or shift-3 combination.
Same is true for almost all other special characters which are used often in
Nim, e.g.: `(`, `)`, `:`, `=`. I do not see how `#` is differ
No way // is too useful as an operator. There's just no need to have a plethora
of alternative syntaxes.
I must keep in mind that I, and anyone, would be using any machine, with any
editor present. That's why I think we must design the language the best way
possible without thinking in something like "why don't you reconfigure YOUR
computer to translate // to #" ?
1. Because sometimes I will use
I thought he was implementing an "operator like" behavior for the string "//",
I couldn't believe it was really used as an operator in the language; now I see
that they used "//" as an initRational() "alias" operator.
Well, I consider this a bad preliminary choice, it's confusing clashing
direc
Rick, I see where you are coming from with this, it makes some sense to me. But
as Araq pointed out, how would you deal with the fact that '//' is a valid
operator? It seems like we shouldn't throw away a perfectly good operator just
to add to the commenting syntax.
Maybe you could configure yo
Nim is full of alternative ways of doing the same.
Preference and style. This will aggregate more people.
I like the language, but I hate the "#" so much (as others) that I decided to
wast some time here to expose this fact, and try to convince Pythonic purists
that there is a huge team of "//"
This doesn't make a lot of sense at all. It might be that you are used to //
comments more than you are used to write # comments, but it is just getting
used to, nothing else. To have two different ways to do the same thing without
clear advantages to one option will lead to diversion in code st
Well... so I don't like Nim anymore.
No way. :D
Nim is... Nimesque. Unique. The block system is Pythonesque, but it has
ADAlisms,
Object-pascalisms, and Cpluspluslisms. The possibility of evolving it to
the better,
aggregating better justified designs is awesome. //- -// is better designed
than the
old /*
Your proposal doesn't work well with the current Nim, // can be an operator:
# let's be even more like Python
proc `//`(a, b: int): int = a div b
echo 3 // 4
And your argument comes down to "I cannot be bothered to use a custom keyboard
shortcut to type '#'".
I don't think your comment syntax should be aded. Nim has a Pythonesque style
it should just keep it. Its not what you add, its what you don't add makes a
great language.
I also don't agree with / / it should just be a C like system with / / and / *
... * / and / * * ... * / not some thing unfa
I write a lot of comments, that's why I give such importance to this topic.
I've explained on the text. The minus "-" is the key right over the brackets on
USA based keyboards, and at a good right spot in almost all accessible in just
one key press. The square brackets, are not available (visually) in some and
you need to find a combination of keys to invoke it. Instead
Actually, I like it. But not sure about //- -//; for me it is much more logical
to be //[ ]// (as direct equivalent of #[ ]#)
Hello,
I also use many different languages, and not a fan of the
Python/Ruby comment syntax "#" :P
First, the justification:
1. Many keyboards does not have an one key access to "#",
as the "/" key, mine for instance, I usually need to look at alt-3
or sh
25 matches
Mail list logo
