Re: tools documentation link is broken

2018-03-05 Thread Araq
Thank you. Fixed.

Re: Introducing moduleinit

2018-03-05 Thread monster
I coded in Delphi, like 20 years ago. If it was my inspiration, then it must have been "unconcious"...

Re: compiler error in 0.18.0 ??

2018-03-05 Thread Araq
Turn of your OS's memory overcommitment. > This seems like a clear compiler error. On the contrary, it looks like a clear programming bug / OOM. > I have no idea why it's doing that, or how to fix it. A full example we can compile&run would be helpful.

compiler error in 0.18.0 ??

2018-03-05 Thread jzakiya
So I'm compiling some new code in 0.18.0. This code code compiles and runs correctly as one process with no problems. proc segsieve(Kn: int) = # for Kn resgroups|bytes in segment ... for indx in 0..5: # for nextp row indexes, var r = i

Re: c2nim fails for struct with function pointer containing reference argument, how to convert manually?

2018-03-05 Thread guibar
Isn't it // foo.h struct foo { void (*bar)(int *fuz); }; or is it a c++ header ? Anyway, you can try something like this type foo {.importc:"foo", header:"foo.h"} = object bar: proc(fuz: var cint) {.cdecl.}

Re: What is

2018-03-05 Thread Araq
There are actually "filters" and "parsers" and "standard" means the standard indentation based syntax/parser. Which is also the default and so the `| standard` part can be left out.

Re: Overloading Module Access Operator

2018-03-05 Thread StasB
I guess the difference is that the meaning of () is disambiguated on the grammar level (or at least I hope that Nim's grammar is unambiguous), while the meaning of . depends on the semantics of a given piece of code, which depend on the context (not that I consider it enough of a problem to just

Re: Overloading Module Access Operator

2018-03-05 Thread Araq
Fair enough, I guess.

Re: Can we use warmer names?

2018-03-05 Thread dom96
This thread has turned off-topic and so I'm going to lock it (any further posts to this thread will be deleted). @libman I would kindly ask you to stop derailing threads into ramblings about how GitHub is communist and other such topics, stick to Nim please. I dislike removing posts so I will k

Re: Overloading Module Access Operator

2018-03-05 Thread Araq
So? `()` is used for function calls as well as for grouping expressions.

Re: Overloading Module Access Operator

2018-03-05 Thread DTxplorer
I can understand aedt rationale. The dot is already used to access objects members. aedt idea made things clearer for me. But maybe I misunderstood the real semantic of these expressions. Anyway, thanks for the tip Araq.

Re: Can we use warmer names?

2018-03-05 Thread StasB
Yeah, that's pretty much what I expected from you. Your entire strategy is to churn out extremely long-winded rants that barely address the core of the issue, **going as far as to respond to earlier posts that have nothing to do with the current discussion, or posts that you 've already responde

What is "standard' in filters?

2018-03-05 Thread KevinGolding
I'm reading the documentation trying to understand source code filters. ( [https://nim-lang.org/docs/filters.html](https://nim-lang.org/docs/filters.html) ) Some of the examples have this line at the top #? stdtmpl | standard I don't understand what the word 'standard' means

Re: Can we use warmer names?

2018-03-05 Thread Libman
This forum is Araq's property, so this conversation here is over. Please don't reply, as this thread getting bumped would increase its annoyance. I apologise that I've gotten drawn into a debate where it isn't appropriate. I'm confident that I've made a correct, complete, and thorough argument t

Re: Can we use warmer names?

2018-03-05 Thread StasB
@Libman: Which of the following statements do you disagree with? * If Bob writes some code (assume he isn't doing so on behalf of anyone else), Bob is producing something that can only be attributed to him * You are **not** automatically entitled to use stuff produced by others * If you use

Re: Overloading Module Access Operator

2018-03-05 Thread Araq
Maybe like this, but it's a bad idea: template `::`*(a, b: untyped): untyped = a.b > And how can I export this operator across the whole project so I don't have > to import the module that defines this every time? Via an `--import:"my_ugly_scope_operator"` in your configuratio

Re: Can we use warmer names?

2018-03-05 Thread Araq
Save the posts you consider valuable somewhere else for I might delete this whole thread.

Re: Can we use warmer names?

2018-03-05 Thread Libman
Dear StasB, First and foremost, please note that **I am criticizing your argument** against my position on NAP and "copyfree"dom advocacy, **not you personally**. Also please keep in mind that this isn't a fully off-topic discussion for this forum, because Nim's ecosystem ranks #1 in "copyfree

tools documentation link is broken

2018-03-05 Thread mitai
from documentation page: [https://nim-lang.org/documentation.html](https://nim-lang.org/documentation.html) Tools Documentation [https://nim-lang.org/docs/tools.html](https://nim-lang.org/docs/tools.html) is broken