Hi @dom96,
I bought _Nim In Action_ a few monthes ago (it was still MEAP v.8), a few days
after install Nim.
I didn't yet find the needed time to study it inside out — too many project to
finish to dedicate myself full time to Nim — but from a first reading I have to
say that the book is
Hello @gneu and thank you for purchasing my book. I have made a conscious
decision to omit some things from the book, Nim is a large language and space
is limited. Unfortunately term rewriting macros/templates didn't make the cut.
The reason is that I personally haven't used them much, as such
Well then let's see if we can re-evaluate their relevance when you're going to
write the second edition... ;)
@dom96: I'm a proud owner of your book since just a few minutes ago. To be
honest, I did not read through this whole thread, so I'm not sure if my
following remark was already discussed: What I'm missing at first look into
chapter 9 is the topic "term rewriting templates". As a novice to Nim
> IMO your rewording of the explanation of forward declaration also leaves
> something to be desired.
Yes, it is difficult to explain, for me, in english. I just tried, as only
complaining is sometime too easy.
For the forward declaration, I think there is already a secret pragma to make
it
@Stefan_Salewski
IMO your rewording of the explanation of forward declaration also leaves
something to be desired. I'd immediately introduce the distinction between
`declaration` and `definition`, and then introduce Nim's rules, hint at why
they make sense, and mention the **possibilty** that
@StefanSalewski My editor assured me that the book will be copyedited
thoroughly by Manning. I am currently looking for factual issues or misleading
sentences. You mentioned some of those, but unfortunately I disagree with most
of them.
I will consider improving the explanation of forward
In case anybody is still looking to purchase [the
book](https://www.manning.com/books/nim-in-action?a_aid=niminaction_bid=78a27e81),
code `wm103016lt` will get you half off today!
Well, writing books in a foreign language is not easy...
You may have noted that this remark from chapter 2 is still not very nice
Order of procedures
It is important to note that the order of procedures and procedure calls
matters.
When calling a procedure, it must be
> Which chapter was canceled?
Chapter 10 Direct Hardware Control
> I was going to buy it, but the chapter that I wanted is now cancelled.
Sorry to hear that. Good news is that I am planning on writing a condensed
version of it as an article.
Which chapter was canceled?
I was going to buy it, but the chapter that I wanted is now cancelled.
So my impression is that you have to do all the work yourself. And what is the
manning contribution?
I just got version 9 of the meap.
I was curious about the actual improvement work of the manning people. My early
expectation was that they would not do much, indeed I think they can not do
much, just because they do not understand the matter. So only a few grammar
fixes remain to them, and I
Last chance to get 50% off Nim in Action! Use code `pbbutcherlt`:
[https://manning.com/books/nim-in-action?a_aid=niminaction_bid=78a27e81](https://manning.com/books/nim-in-action?a_aid=niminaction_bid=78a27e81)
> Hi @dom96! > Just ordered the book. Thank you for the discount!
Thank you for ordering it!
> Because now to understand which methods for example the seq type supports the
> fastest is to use Internet search. setLen is in system, some others are in
> sequtils and etc.etc.
Keep reading, i'm
A reference on collection makes no sense, but showing how to work with standard
collections is a rather fundamental part of showing a programming language, in
my opinion
Hi @Stefan_Salewski!
> In a book that makes absolutely no sense. >... > For Nim -- use one of the
> many editors with great nimsuggest support.
I now consider Nim for writing fast server-side scripts. And we have a park of
headless servers with ssh-only access.
So you can imagine how uneasy
> Probably it would be good to have in the book some short reference of Nim's
> collections API.
In a book that makes absolutely no sense. I have a few computer books where
such type of references exists, a prominent example is the GTK Book of Mr
Krause. These people had trouble to fill the
Hi @dom96!
Just ordered the book. Thank you for the discount!
* * *
Probably it would be good to have in the book some short reference of Nim's
collections API.
Because now to understand which methods for example the seq type supports the
fastest is to use Internet search. `setLen` is in
Nim in Action is 50% off until the 25th of August using code `pbbutcherlt`:
[https://manning.com/books/nim-in-action?a_aid=niminaction_bid=78a27e81](https://manning.com/books/nim-in-action?a_aid=niminaction_bid=78a27e81)
Perfect opportunity to grab it if you haven't already. It's almost finished
Hi @dom96,
I just purchased (pre-ordered) Nim in Action from my local Chapters bookstore
and am pretty excited about getting the book. Do you know if it is possible for
me to access the MEAP pdf's of the existing chapters on the Manning site with
an in-store purchase? I don't know if I would
I think I've answered my own question. I saw on the Manning webpage:
> Q: Can I buy a MEAP anywhere else?
>
> No. Currently, MEAPs are available exclusively at manning.com.
So looks like I'll have to wait until January. Oh well, it'll be a nice New
Year surprise.
> Should we also have "Ben".cstring?
You don't need to do it, because "Nim string values will be converted to C
strings automatically" for `{.varargs.}`.
Thank you **@moigagoo** for your feedback!
> 1\. In 8.1.3 Type compatibility, you point out that we can't use int and
> string and should use cint and cstring instead. But instead of explaining the
> differences, you state that cstring is actually similar to string (to the
> point where string
AFAIK the "c" in `cstring`, `cint` etc. means "compatible" so it makes some
sense.
@Stefan_Salewski
> The %d should refer to a cint. Should we have to provide 30.cint for the
> argument?
Should we also have `"Ben".cstring`?
> About the {.importc.}, {.importcpp.}, cstring thing, they should really be
> called {.importnp.}, {.importnoo.}, nstring, etc, where n means "native", np
> means "native procedural style", noo means "native object-oriented style". Or
> even better, {.import.}, {.importoo.}, and nstring
> But instead of explaining
>From Araq's manual we know
proc printf(format: cstring): cint {.importc, varargs, header: "".}
var n: cint
n = printf("My name is %s and I am %d years old!\n", "Ben", 30)
echo n
This works fine for me, but I still have to
About the `{.importc.}`, `{.importcpp.}`, `cstring` thing, they should really
be called `{.importnp.}`, `{.importnoo.}`, `nstring`, etc, where `n` means
"native", `np` means "native procedural style", `noo` means "native
object-oriented style". Or even better, `{.import.}`, `{.importoo.}`, and
I just finished the new chapter and wanted to share some feedback.
1\. In 8.1.3 Type compatibility, you point out that we can't use int and string
and should use cint and cstring instead. But instead of explaining the
differences, you state that cstring is actually similar to string (to the
> I think fewer words with the same meaning are easier to understand.
I agree, although @OderWat's suggestion is too succinct :)
I will do my best to shorten that sentence. I'm fairly sure that Manning's
proofreaders/copyeditors will also flag up these issues to me before the book
goes to
I think that says the same thing more succinctly ... and I think fewer words
with the same meaning are easier to understand.
Well I guess:
> To (successfully) wrap the (required) procedures, you have to define four
> types.
would be enough. But my english isn't good either. So what do native speakers
think about that?
> Before you can successfully wrap the required procedures, you are going to
> have to first define four types.
I don't see anything wrong with this sentence.
> One of the biggest advantages that a language which can be translated to
> JavaScript but also used for writing desktop applications
It is not very easy to read for me as a non native speaker unfortunately...
> Before you can successfully wrap the required procedures, you are going to
> have to first define four types.
>
> One of the biggest advantages that a language which can be translated to
> JavaScript but also used
Looks like the deal is still available with the code `wm070216lt`.
For anybody still looking to buy Nim in Action, you can use code `wm070116lt`
today to get 50% off
[https://manning.com/books/nim-in-action?a_aid=niminaction_bid=78a27e81](https://manning.com/books/nim-in-action?a_aid=niminaction_bid=78a27e81)
**@moigagoo** thanks, will correct!
39 matches
Mail list logo
