> It seems to be valid Nim code.
That's what I wanted to know, thanks!
> It's also a design right from the 90ies, slow, impossible to parallelize,
> hard to serialize.
I know. I wouldn't have come up with the design if I wrote it myself, because
it is a straight port of the Python tutorial
So, what I basically want to know is if what I wrote is valid and sound Nim
code.
It seems to work, though.
Thanks!
I searched for 'concept' but it failed me - I even looked at the section you
linked to, but managed to overlook the (prominent) section on concepts ;p
Yes, even though I am a programmer - and thus prone to overthinking - I guess
I'd get the basics down before moving on to unchartered
> Generally Nim's docs = [..] concise and legible.
Exactly. And one of the main reasons why I have decided to prefer Nim
Any good docs on concepts in Nim ?
I failed to find it in the tutorial - perhaps I should browse the manual as
well ?
I am very new to Nim, and am trying to port the libtcod tutorial written in
Python - here: [Complete Roguelike Tutorial, using
python+libtcod](http://www.roguebasin.com/index.php?title=Complete_Roguelike_Tutorial,_using_python%2Blibtcod)
\- to Nim.
For the most part, it is smooth sailing, but
This is an odd request
Yes, there are languages that _has support for audio read/write_ \- but the
point is that those languages has that support by means of packages/libraries -
that kind of functionality is never in the core language.
So, if Nim doesn't have it, I guess it's because Nim
I agree - Nim is a community driven project, like many open source projects,
and it gets better only if you scratch your own itch. Small improvements to the
documentation is, like dom96 says, a perfect way to start contributing.
[Edit] I agree that not everyone is command-line ninjas, and I
I think that _configuring the PATH environment variable_ is more than enough,
to be honest.
It is something that most (perhaps even all?) developers needs to learn how to
do, regardless of the operating system.
Get off my lawn, dude. Passing a tuple to a factory proc is definitely a neat,
and clean, thing to do.
You can construct a tuple and pass it in, and use that to construct an object.
Much neater than a huge parameter list, I think.
Sometimes.
It depends. As always.
Are you sure you want to
For what it's worth, I have built Nim several times without incident on my
Debian box - following the instructions to the letter - so I guess the problem
you have is specific to your machine.
Creating an object from a tuple using a macro is actually very neat!
> "let's have a simple core but metaprogramming"
I like that, a lot!
I don't care about Ada either
What I would like is a language that is expressive and as simple as possible -
I hope that the C / C++ "backend" will stay - and Nim is that, to me.
I don't need any more selling points, to be
I disagree.
I would like to have more Nim programming videos - those are great to make
people discover Nim.
Personally, I don't really like too much sales pitch - I grew really tired of
Rust and their happy slogans (Hack without fear - zero cost abstractions) those
gets old really fast!
I
v1.0 **_should_** remain elusive - that's how it works in Open Source.
As for replacing C ...
I don't know.
I've been programming in C++ for years, and recently grew so fed up with it,
that I took up C.
Modern C is really, really neat, and not something that needs to be replaced
IMO.
C++,
> That is precisely what's happening
Excellent!
I'll carry on with Nimble, then
Thanks, Andrea, for confirming my thinking.
To me, it makes a lot of sense to let a package manager handle builds, versions
and dependencies, and it looks like that Nimble is slowly obsoleting Nake by
incorporating most (all?) of Nake's features. At the very least it can explain
the overlap
> will compile not only your_program.nim, but also all imported modules
> recursively and build the final complete executable, so most of time you need
> just the compiler to build your project.
That is true, and also how I started out - mainly due to the fact that the Nim
tutorial does not
The reason I am confused is because if nimble is able to handle builds (nimble
build) I would rather not have to deal with nake, if I can help it.
Nake is probably more fully featured, but my needs are simple.
Since I am totally new to Nim, I thought I'd ask you guys for advice.
Are you using
I am a bit confused about the difference between nake and nimble when it
applies to project management.
Coming from Rust, where I am used to use Cargo to manage my projects/builds.
I am currently using 'nimble init' to kick off a new Nim project, but I am
aware of nake, which is a build tool.
It's a pity that the Americans somehow managed to transform the concept of
Nimrod from a God to an Idiot
Nice!
I can't get enough of videos about Nim and graphics programming!
22 matches
Mail list logo
