Re: A couple of questions

2019-11-11 Thread treeform
"Is there a ncurses kind of library with Nim?" YES [https://github.com/rnowley/nim-ncurses](https://github.com/rnowley/nim-ncurses) Second of all, what is nim's object model? Nim does support object oriented programming. Many libraries don't use and go for C or Pascal style struct/generics/poly

Jetbrains IDE support?

2019-11-11 Thread jawlingomes
Does anybody knows a way to have Code Completion, Syntax Highlight, Auto-indent, Code folding and other utilities with any Jetbrains IDE? I'm using Intellij IDEA, and the only existing plugin for Nim does not do any of that.

A couple of questions

2019-11-11 Thread NuzakFarnas
Hi all, recently I wanted to try and write a text-based app, like nano, and play around with it (on Linux). I wanted to try it with Go, but after having a hello world have 1.3M bytes of text, I decided it was a bad idea, so now I'm here. First of all, is there a ncurses kind of library with Nim

Re: Play audio in Nim ?

2019-11-11 Thread mikra
there is also a modplayer for nim : [https://github.com/johnnovak/nim-mod](https://github.com/johnnovak/nim-mod)

Re: Play audio in Nim ?

2019-11-11 Thread treeform
I made some libs fro that: Low level: [https://github.com/treeform/openAL](https://github.com/treeform/openAL) High level: [https://github.com/treeform/euphony](https://github.com/treeform/euphony)

Re: Get contents of directory at given path

2019-11-11 Thread cdunn2001
But if you have large numbers of files, note that you really can't beat the speed of UNIX `find`, as it has a special, tricky optimization. I sometimes stream `find` into Nim.

Re: A super newbie git-related question

2019-11-11 Thread cdunn2001
Here is a good way to think about Git: * Subversion (or Perforce) stores changes but make you think about files. * Conceptually, it's a tree of files. * Git stores files but makes you think about changes. * Conceptually, it's a tree of deltas (like UNIX patch-files). When you rebase

Re: A taxonomy of Nim packages

2019-11-11 Thread Stefan_Salewski
Thats works! I have moved RTree from Graphics algorithms to Data structures . I do not fully understand the sorting in each category, seems to be mostly alphabetical, but not strict, and what is about lower case and upper case? You wrote about prefering pure packages. Note that wNim and gintro

Re: What is the difference between "writeFile" and "newFileStream" and "write"?

2019-11-11 Thread nnahito
Thank you reply! I used the nim language 1.0. 0. As you pointed out, I will update to 1.0. 2. Thank you!

Re: A taxonomy of Nim packages

2019-11-11 Thread spip
Instead of depending on external Github repository, I've moved my curated packages list to Nim's wiki: [https://github.com/nim-lang/Nim/wiki/Curated-Packages](https://github.com/nim-lang/Nim/wiki/Curated-Packages) Now everybody can contribute. No need to wait for PR being merged: you just need

Re: Bioconda

2019-11-11 Thread cdunn2001
* [https://github.com/nim-lang/Nim/wiki/Bioconda](https://github.com/nim-lang/Nim/wiki/Bioconda) `conda install nim` basically works, but only for Linux64. And it needs improvement.

Re: Nim for Statistics

2019-11-11 Thread Usor
@Lecale, in that case, thanks. @mikebelanger, no, I haven't, due to lack of time for it. It does look good. @mratsim, then we seem to more or less concur in general and that Nim & ecosystem are not ready at the moment, while they look very promising. I wish I could help out with these endeavour

Re: Nim for Statistics

2019-11-11 Thread Usor
Maybe you should rant more? I at least don't mind :P

Re: A taxonomy of Nim packages

2019-11-11 Thread Vindaar
I just opened an issue on the awesome-nim repo about adding a few more collaborators, so that PRs can be merged more quickly. [https://github.com/VPashkov/awesome-nim/issues/65](https://github.com/VPashkov/awesome-nim/issues/65)

Re: A taxonomy of Nim packages

2019-11-11 Thread Willyboar
Well, there is a two-month-old PR waiting to merged. I think awesome-nim is a very important resource for newcomers. Personally, it was one of the first repos I checked when I found nim. Also, I agree with @kidandcat

Re: How to package external packages into a single standalone binary

2019-11-11 Thread federico3
Nim favors static linking by default. If bignum has no runtime dependency on any shared objects (DLL) the binary contains everything you need to run. Static linking comes with some disadvantages, for example that end users need to update the whole application every time a critical issue is fixed

Re: How to package external packages into a single standalone binary

2019-11-11 Thread gemath
If you deploy with nimble, [https://github.com/nim-lang/nimble#binary-packages](https://github.com/nim-lang/nimble#binary-packages) covers it.

How to package external packages into a single standalone binary

2019-11-11 Thread drkameleon
I make use of an external dependency (bignum: [https://github.com/FedeOmoto/bignum](https://github.com/FedeOmoto/bignum)) which I've install via nimble install bignum. And every compiles and runs fine - locally. If I deploy my mac to run on a different machine, the bignum library is missing an

Re: A taxonomy of Nim packages

2019-11-11 Thread mratsim
Is it? if you open a PR, it's quickly merged last time I tried.

Re: let & const on C backend

2019-11-11 Thread foldl
I am following your RFC. In my opinion, let variables are already "readonly" once they got assigned. {.readonly.} pragma seems a little bit redundant. The problem here is that, from the perspective of nim compiler, when to initialize let variables? While some can be initialized in compile time

Re: Domain modeling in Nim

2019-11-11 Thread RedFred
> UML is not traditional software engineering, it's a big business approach to > software, often associated with waterfall design. Not true. UML is just a notation. How you use it is up to you. It's used successfully in agile/scrum cycles to illustrate a design or a solution in commonly underst

Re: A taxonomy of Nim packages

2019-11-11 Thread kidandcat
Like I always say, the awesome-nim repo should be under the nim org, then if all core maintainers are busy even for accepting PRs, add external collaborators, but keep the repo under your control if that person disappear.