> But forbidding tabs I don't like.
You stated you use gedit, which handles indentation (via the tab key) with
either spaces or tabs, and that is very simple to configure.
Most decent editors have this feature. For me I prefer Nim not allowing tabs. I
don't see the point of having tabs used
> With your backend, would it be possible, to also compile nimscript and macro
> code to native istructions and throw out the distinction of runtime and
> compiletime behavior?
Even if you are not using C as an intermediate step it is still essential to
distinguish between compile time and run
> If I would think Go is the future, I would not be here.
Heh... Same with me. Go might have a future, not much of one with me however.
> ... With the result that cstring now means compatible string.
Yeah, I reached a similar conclusion (on all the **c** prefixed types, as I
have used **nim
In regard to where these should go.
> We also have a linux.nim module for Linux specific stuff.
Well, these came from BSD. I will check if these are are available on Darwin as
well, as I will also be targeting MacOS X.
> CONFORMING TO
>
> These are BSD functions, present in glibc. They are
Well, strictly speaking, these are not Posix.
>From the Linux man page:
ATTRIBUTES
For an explanation of the terms used in this section, see
attributes(7).
┌─┬───┬┐
│Interface
Alright, this is what I got working for the posix stuff:
{.passL: "-lutil".}
var SIGWINCH* {.importc, header: "".}: cint
var TIOCGWINSZ* {.importc, header: "".}: cuint
var TIOCSWINSZ* {.importc, header: "".}: cuint
proc openpty (amaster, aslave : ptr int,
Ok, I'll need to move the definitions/code to pure nim first and get them
working that way. Some of these may not be available on all posix systems.
Right now I'm just targeting Linux for the code that uses those, but I'll be
targeting MacOS X as well.
Oh, I really like it how one can use nim
Well, I'm not been active here or in #nim on freenode lately, but I've been
using Nim a lot at work.
I'm on a new project (rather significant one), and I decided to do a majority
of the new software required by it in Nim.
Tried to do one component in C++, as it required a lot of posix stuff,
