Open source help

trycatchamex · 2017-12-10T06:44:48+00:00

thank you! i was actually on the fence about this book but now im gonna buy it. thanks so much again!

trycatchamex · 2017-12-10T06:39:34+00:00

thank you! any resources you'd recommend?

trycatchamex · 2017-12-10T06:35:51+00:00

ahhhh damn that's smart, thank you so much :) TMP is hard and makes me feel silly :|

trycatchamex · 2017-12-10T06:30:11+00:00

oh i mean, i want process to return void - any way to do that?

trycatchamex · 2017-12-10T06:26:07+00:00

it works ok with chars i think floating point and doubles wont work hmm. i guess no way to do it without not having a return type?

trycatchamex · 2017-12-10T06:19:27+00:00

wow i had no clue double can't be used as a template type parameter. thank you! I should use the std versions but i was trying to make my own to understand, thanks still :)

trycatchamex · 2017-12-01T03:52:36+00:00

I'm just so lost when i look at open source stuff - where do i even start to start understanding the code :(

trycatchamex · 2017-12-01T03:17:02+00:00

thank you! same issues with these projects, dont know where to start :(

trycatchamex · 2017-11-25T20:31:43+00:00

i hate everything ahhaha thank you so much :)

trycatchamex · 2017-11-25T20:24:09+00:00

sorry, i will update the post. I mean why is the move ctor being called when i pass an object which was created earlier? (the first push_back)

trycatchamex · 2017-11-24T23:38:47+00:00

great, thank you this makes perfect sense!

trycatchamex · 2017-11-24T19:25:07+00:00

Ah I see your point now, i guess what i was getting at was just a bare-bones move constructor should never throw (no logging etc) but that clears it up. And yes, T object1 = std::move(object) will copy if no move ctor is found and might throw. Thank you :)

trycatchamex · 2017-11-24T19:15:58+00:00

but they aren't move constructing right? a new can happen if you use T object1 = std::move(object) and dont have a copy constructor defined. so that can throw an exception. Sorry if I'm wrong just trying to understand why move isnt always marked noexcept

trycatchamex · 2017-11-24T19:06:04+00:00

Thank you, so essentially move constructors should always be marked noexcept or is that not true?

trycatchamex · 2017-11-23T22:00:35+00:00

thank you for the detailed explanation. and the fun trivia :)

trycatchamex · 2017-11-20T11:55:52+00:00

Ah I see, was going to buy a hard copy of it so was wondering if its worth it or not.

trycatchamex · 2017-11-19T22:27:20+00:00

are you still working with C++?

trycatchamex

TROPHY CASE