In the new nim 19.0, nil and seq of length 0 are the same. So you should not
run into this as often.
These are now all valid and work:
var a: seq[int]
a.add 1
var b = newSeq[int]()
b.add 1
var c: seq[int] = @[]
c.add 1
Run
initializing al
oh! our replies overlapped. the "armv7a" sounds more familiar in the beaglebone
arena, so I started with the arm7. but just now I discovered that the arm6
version worked... built my project and it runs successfully. So, thanks again.
I may try the "armv7a" in the future.
Looks like DockCross has a special image just for the beaglebone -
dockcross/linux-armv7a.
You could try the nightlies script and use that image instead and see if it
works for you as is.
WHOOP! got it!! thanks a heap!
Thanks!, that looked promising at the start. but, the arm7 version of "nim" or
"nimble" on the beaglebone responds only with
Illegal instruction
Run
I'll try the arm6 version next
Not sure how helpful this will be but I just enabled ARM binary builds in
[nightlies](https://github.com/nim-lang/nightlies/releases) using DockCross.
I do have to make some changes to nim.cfg for this. Check out [this
script](https://github.com/nim-lang/nightlies/blob/master/dx.sh) which does a
I've painlessly used the "How I Start" (
[http://howistart.org/posts/nim/1/index.html](http://howistart.org/posts/nim/1/index.html)
) build instructions link from the Nim doc page a bunch of times on ARM
devices over the past few years. But, just now when I really need it to work,
I'm having tr
I know this is old, but initializing all seq[] with a dummy variable then
wiping them before their intended use seems to work for me.
Great, thanks for the feedback - so I've given it a proper Nimble structure,
and started writing some tests. My god the bugs.
One thing I've been wondering about is how to structure attributes vs contents.
Take a feed element like this:
> uri="[https://github.com/dom96/jester](https://github.c
That logo is the mark of a visionary man.
Actually printer is good for everyone. And it helps to know about it easily.
Faced any type of issue with canon printer then I have
[https://errorcode0x.com/solved-canon-printer-error-code-1660](https://errorcode0x.com/solved-canon-printer-error-code-1660)/
> it sounds for me like proc[urrent] not like proc[essor]
Actually, it is short for proc[edure]. What does procurrent even mean?
12 matches
Mail list logo
