Great day for all of us that love Nim! And the big good news for our Nim are
yet to come!
Cheers to all Nimsters!
Great news (1.0 RC) and thanks to all that made this possible. Horay! horay! -
Nim 1.0 is near!
Really nice console, like it
Yes, Windows console is set by default to regional (non unicode) code page.
Anyway it is good practice if you change codepage then restore it on exit, you
never know what legacy (but very very important to somebody) software depends
on it :)
Or just compile nimpretty yourself:
cd
nim c -d:release -o:./bin/nimpretty.exe ./nimpretty/nimpretty.nim
Run
You can, but string literal for unicode is "u" (exactly four hex digits),
not "x"
I would not say that Nim has perfect support for Unicode in Windows console
because it hasn't. Neither input, nor output of unicode chars works out of the
box in any version of Windows from WinXP x32 ANSI to Windows 10 x64 Unicode.
But actually it is not Nim fault, but creepy Windows/MSDOS
Thanks to all supporters that voted for adding Nim in repl.it: hip, hip, horay,
[it is
done](https://repl.it/talk/announcements/Two-new-languages-Nim-and-Crystal/11886)!
[Try it](https://repl.it/languages/nim)
Unfortunately for the last two builds only Windows x64 was built
Very strange and sad: several last 19.9 nightlies
([v0.19.9-9e68b2c](https://github.com/nim-lang/nightlies/releases/tag/v0.19.9-9e68b2c)
\- 10 hours ago,
[v0.19.9-f5cc2e2](https://github.com/nim-lang/nightlies/releases/tag/v0.19.9-f5cc2e2)
\- two days ago,
My bad, I am using 32-bit Nim only and never tested wAppbar under 64-bit. I
will be glad to receive your pull requests
Great job!
://github.com/zolern/wAppbar](https://github.com/zolern/wAppbar)
\---
* wAppbar is Nim/wNim implementation of Windows Desktop Appbar (custom bar that
stays on top of other applications, like a Windows Taskbar)
Great work! And one big step closer to Nim 1.0.0
Awesome work! I will try it in my next project
Great news for Nim, for the Nim developers and for us all that love Nim. Kudos!
It is not Nim specific problem, you know, it is in general GUI "problem".
In my practice the best way to send some data (and when I say "data" I mean
"more than DWORD value") to UI is to save that data in some temporary container
and use "message to ui" just to say "Hi, here is some data for
VSCode rulez! I tried almost every Windows-based editor that supports Nim and
VSCode is my favorite. VScode is great in so many ways! And many thanks to
Kostya Zaitzev, Nim plugin's author, for awesome work.
Notepad++ from version 7.5 has embedded support for .nim files (syntax
highlighting and code folding). NB: in release notes for 7.5 Nim still is
called Nimrod
@LeuGim I mean that LLVM/clang's pow is much faster than gcc's pow and not just
in this particular case pow(-1, n), but is faster in general.
Wow, final "ready for print" edition is pretty awesome. Great work!
I am pretty sure that Julias's POW takes care that first argument is -1 and
optimized it with something like MOD You can check it, I suppose that modified
Julia code with MOD will take pretty same time as code with POW.
Well, my 10 cents
import times, math
proc leibniz(terms: int): float =
var res = 0.0
for n in 0..terms:
res = res + (if n mod 2 == 0: 1.0 else: -1.0) / float(2 * n + 1)
return 4*res
let t0 = cpuTime()
Good job. I just needed nim module that works with COM
I am just curious why chrome and doc procedures return strings. If you not need
result of these procedures just not set type of return value. And yes, if you
need these strings you should use them or discard them.
And if you want to echo result of procedures I can suggest a variant with
"case"
I am afraid -o option doesn't set directory for binary. I tried it when I set
my VisualStudioCode to save compiled binaries from all my projects in one
folder, but -o expects also filename.
Hooray, nimers!
Wow! I knew that Nim is fast, but SO FAST? Nice
New site is just great! Wow, my lovely Nim becomes better and better in every
aspect!
Actually, I like it. But not sure about //- -//; for me it is much more logical
to be //[ ]// (as direct equivalent of #[ ]#)
Greetings and respect for Zahary (BG rules!) I am sure the best with Nim is yet
to come
Nim CG also is thread independent
And only when compiled with MinGW. When compiled with vcc - no problem. Very
strange :(
May be it was good to refine that this happens on Windows (I tested it on
Windows XP, Windows 2003 and Windows 10)
frwite works perfect in local codepages (non 65001). fwrite works perfect in
files. fwrite outputs incorrect only when non ASCII symbols are outputed to
stdout.
Example:
proc getConsoleOutputCP(): cint {. importc: "GetConsoleOutputCP", stdcall,
dynlib: "kernel32" .}
proc
35 matches
Mail list logo
