Zhejiang Licheng Printing and Dyeing Machinery Technology Co., Ltd. specializes
in producing all kinds of printing and dyeing machinery and equipment such as
[url=[https://www.hotairstenter.com/product/hot-air-stenter.html]Hot](https://www.hotairstenter.com/product/hot-air-stenter.html\]Hot)
Air
I might need to break up the "Non-English" playlist by language...
There's now [a lot of new Nim YT videos in
Thai](https://www.youtube.com/channel/UCTyvSBAvdBPDS-7isD5GDdw/videos)! 🇹🇭👍
You arrive like an angel from heaven. In fact, I have been experimenting with
the Android NDK lately, and it was extremely terrible. Your project seems like
an enlightenment.
You can ignore `{.locks.}` pragma. It's only important when you use the `locks`
module and/or the [guard
system](https://nim-lang.github.io/Nim/manual_experimental.html#guards-and-locks).
It's one of the most misleading thing in the error message, where it bears
zero significance.
Same as with
> GNU Affero General Public License v3.0 😤👎👎👎
Pretty much the best license out there, for network apps.
Hi all,
I've installed AnyDesk 4.0.0 on Ubuntu MATE 18.04, which is fully updated.
If my Ubuntu machine is logged into the desktop, unattended access works
absolutely fine. However, if I try unattended access with the Ubuntu machine at
the login screen, I can connect and the mouse works fine, b
As to the problems I see with docs, please note I [already took some effort to
try and explain them](https://forum.nim-lang.org/t/4523#28911), but it feels to
me like it was dismissed or ignored. So I find it hard to muster more energy to
try and explain it again, maybe in different words, if it
If you are using Windows x64 and you add `--os:windows --cpu:amd64` options,
Nim still runs as native compile mode. Then, `amd64.windows.gcc.exe =
"x86_64-w64-mingw32-gcc.exe"` in .cfg file is ignored. If you still want Nim to
call `x86_64-w64-mingw32-gcc.exe` rather than `gcc.exe`, add `gcc.exe
What are you too talking about? I'm on Windows and I have all C toolchains
working as expected. I can't make Nim compiler use the right toolchain for each
of four targets, it uses gcc.exe for some reason. Please read the post before
answering.
Well it was not easy trying to get this working and after several segfaults and
illegal indexes i (finally! RTFM!) looked into some more documentation but
really couldn't find much about working with dynamic libraries created in Nim.
What I did see is that more people had the same problem in thi
WSL provides a nice convenient way to compile on Linux.
The package is entering Debian Experimental right now. I'll upload it to
Sid/Unstable after some testing and later Ubuntu and other derivatives.
To crosscompile to windows you just need to provide -d:mingw
@akavel, from your comment on lobste.rs:
> this may be solved if there’s some IDE support (i.e. “go to definition”)
> available; I haven’t searched for it yet.
I've successfully used go to definition, both in VSCode and Neovim (with
[nim.nvim plugin](https://github.com/alaviss/nim.nvim)).
> Th
very gay and dumb #MAGA
Fantastic work for a "hobby" project! I'm impressed!
And now the closure thing:
... gn.nim(93, 20) Error: type mismatch: got
... but expected one of:
... proc (...){.closure.}
Run
The parameter looks like this: p: ProcType where ProcType is:
type ProcType = proc(a: int, ...):
Nevermind, the backend code needs to be patched for this.
Error: illegal capture 'variableX' because 'callbackFunction' has the calling
convention:
The only way is to turn the callback functions into normal global functions but
it's an awful solution and not what I want.
Hello
If I have code like this:
var fn0 = proc (x: int): void = echo(x)
Run
it will expand into this:
var fn0 = proc (x: int): void {.gcsafe, locks: 0.} = echo(x)
Run
and if I try this:
fn0 = proc(x: int): void =
#callin
So okey, I'm on windows, I have 4 toolchains in PATH:
* i686-w64-mingw32-gcc.exe - targeting native Windows i686
* x86_64-w64-mingw32-gcc.exe - targeting native Windows x64
* i686-linux-musl-gcc.exe - targeting Linux i686 from Windows
* x86_64-linux-musl-gcc.exe - targeting Linux x64 from
Unless you have some serious medical condition which would affect your bone
healing you most likely can have implants. Metal free dental implants are quite
popular as they are better than metal dental implants. They are more reliable
and have a long life span. There are many techniques of doing
Updated Docker images:
[https://hub.docker.com/r/nimlang/nim/tags](https://hub.docker.com/r/nimlang/nim/tags)
Teeheehee, *snicker* how do you know so well what I picture in my head? :D :P
But uh, oh, _sh,_ please note the formal business-speak term is **" a
pipeline"** :D :D ;P
Almost 8 months after the release of v0.19.0, here is the third bugfix release:
[https://nim-lang.org/blog/2019/05/13/version-0196-released.html](https://nim-lang.org/blog/2019/05/13/version-0196-released.html)
If you use choosenim, the new version is just `choosenim update stable` away,
otherwi
Sounds like a Rube Goldberg machine :P
Thanks for the good words! :) I don't really find it large nor complex, each of
the tools proved to be surprisingly simple and not doing too much after
exploring their code; though now that you say so, I maybe haven't conveyed this
well enough in the code of the dali assembler in particular; may
27 matches
Mail list logo
