@moigagoo sure thing, sounds like a plan to me :)
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.
@guitmz I'd be happy if instead of abandoning the task completely you'd join
this new repo :) If you're game, I'll be happy to add you to the repos on
GitHub and Docker Hub.
@OderWat I was looking for examples online, because I remember that one of the
c++ talks mentioned that they completely forbid the usage of templates. But I
can't find that specific talk anymore. I saw too many, and did made a protocol
about talks I watched. But what I did find is first of all,
Good work! I just tried it some minutes ago with the new Docker client on Mac
and it works pretty well and easy.
BTW: For beginners which just try it out you may add how to access devel or
other versions in your compilation example. I just saw that you have this info
on the Nim website but not
**UnnoTed**, because that way it's more interesting?
**Vladar**, why not just make bindings for a already existing one like
[http://www.raylib.com](http://forum.nim-lang.org///www.raylib.com)/ ?
**rational**, since there seems to be a demand for it, I'll try to carve out
some time to start it sooner. Watch out for announcements.
**hcorion** nimgame is deprecated since sdl2 came out. I just updated it to
support Nim v0.14.2 and you could use it as a kind of reference though, but I
plan to create sdl2-based engine in the future, when I'll get time for this.
Another solution:
import future
type
MyInterface = ref object of RootRef
foo: proc(this: MyInterface): int
bar: proc(this: MyInterface): int
proc foobar(this: MyInterface): int =
return this.foo(this) + this.bar(this)
type
@Krux02
OK. If you're worried about code bloated, the best way is not to use interface,
try functional programming （object-oriented programming is inflexible）:
import future
type
MyImplementationA = object
MyImplementationB = object
m_foo,m_bar:
12 matches
Mail list logo
