| |
| |
| |
|
Page: 1 2 3 4
Comments:
<0> I understand this is a channel on c++, but I just wanted to know if the language "Autoit" is helpful in game dev..?
<0> Can anyone help me with somthing?
<1> Gattsu, your question was stupid so we're ignoring you.
<2> I understand this is a C++ channel, but would anyone like to discuss using buttplugs as a nonsymmetrical fashion style?
<3> Zenethian-: you want an off topic question?
<4> haha
<4> CrewdenX: sorry, I was mocking someone from earlier that you missed.
<5> why nonsymmetrical?
<3> Zenethian: ok
<4> Why not? :D
<5> maybe you have 2 ***holes?
<5> .. i take that as silent commitment :)
<6> pfft
<6> C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do, it blows away your whole leg.
<7> when doing boundary checking, how can you prevent infinite looping if the user enters a character? For example, i have a loop that gets user input while the input is outside the interval [0, 3], but if I enter a X, my loops iterates infinitely. How can i prevent this?
<7> the input should be an integer
<1> Er, you need to reset the stream state if it ****s.
<8> hai all
<8> hai all+GYK+
<8> +
<8> '/
<8> do
<8> u
<8> kno
<8> w
<8> GYK
<9> hm...
<9> Reth, why didn't they design basic_string with a guarantee on operator[] for s[s.size()] to be 0?
<8> sup
<8> anyone here
<10> yep
<8> hi illuminatus
<10> sup
<8> ****er
<10> hah
<9> s/and/an
<8> hehe
<8> *peace*
<10> hey teq
<9> heya
<10> that's intense
<9> nicest looking design I've found in a while: www.bartelme.at
<10> thanks
<11> Hey
<9> yo
<12> mornin' RobotBebop
<12> oh, and tequilla
<9> hola Meekys
<11> Nobody alive ?
<11> Hey Meeks, Glen
<12> nah, no one alive
<11> Heh
<12> nah...
<11> heh
<11> Whoa
<11> The +o returns
<11> :)
<11> I wish the girl that digs me was at the party i was at :(
<9> how's life?
<11> Not so bad
<11> Can't complain
<11> Do you realize??
<11> That we're floating in space o/`
<13> but what is space floating in?
<11> I dunno
<11> don't you listen to the flaming lips ?
<9> only the fiery eyeball in the sky
<9> oh wait, the stupid Hobbits killed that.
<13> I think I damaged my soundcard
<13> I guess playing a 40Hz sine at full volume wasn't a good idea
<11> eh?
<13> eh?
<11> buh?
<13> buh?
<14> do anyone know this _|_
<10> looks like my cock
<14> hehe hey illuminatus
<14> u still there
<10> yea
<10> yea i'm still here
<10> downloading counterstrike
<9> I bet RobotBebop does a /whois scalar
<9> before joining #C++ :P
<10> why
<10> are they gay lovers?
<4> just you and I baby
<14> ?
<10> LOL
<9> don't let Zenethian fool you
<9> his gay lover is a guy called Wayne
<10> am i the only straight guy in here?
<4> hehehe
<10> i wonder what would happen if you put a previously-trained soldier in bootcamp
<10> he'd probably beat the **** out of the drill sarge
<13> what is technorati?
<10> some left-wing propaganda news network
<10> or blog
<13> somehow a blog post of mine go on there
<15> hi.
<1> Hm
<1> +e?
<9> exemption for him, since we have qualitynet akicked
<1> Oh yeah.
<16> is there some library out there that provides a draft implementation of tr1
<1> I think Boost has the closest thing to one that's freely available.
<1> I mean, most of the libraries were theirs to begin with.
<16> I like shared_ptr a lot
<16> but I was hoping that shared_array would make it in there too.. so you wouldn't have to use shared_ptr< vector <T > >() in place of shared_array
<1> You can use shared_ptr with an array deleter.
<16> how do you mean
<1> struct delete_array { template<cl*** T> void operator() (T* a) const { delete[] a; } };
<1> std::tr1::shared_ptr<char> p(new char[5], delete_array());
<1> You only need one delete_array, and can put it somewhere safe.
<1> :)
<16> interesting
<16> I'm also a little confused about weak_ptr
<16> When is it appropriate to use weak_ptr ?
<1> When you don't want your reference to the pointer hold on to it.
<16> just access?
<1> Basically, if you have a shared_ptr to an object, that object won't go away. If you have a weak pointer to it, it might go away, in which case the weak_ptr will nullify itself.
<16> interesting, thanks for explaining that.
<1> It's really useful for detecting cycles of objects, and occasionally useful if you have some kind of cunning scheme where things "magically" update, as an implementation detail.
<16> well i've used auto_ptr, I used it fairly recently to transfer ownership
<16> rather than some other kind of hack
<16> that's error prone
<1> Well, auto_ptr is also error prone, but yeah.. I do the same thing. It's good style.
<1> It'll be much better when we get move_ptr in C++0x.
<16> what is it
<1> It uses rvalue references and move semantics to prevent the kinds of problems that are seen with auto_ptr.
<16> what kind of problems
<1> With move_ptr, you can return it or p*** it to a function to transfer ownership, but copying and ***igning from an lvalue won't compile.
<16> I think auto_ptr is, at least, relatively straight-forward ;p
<1> The canonical example involves calling sort on an array of auto_ptrs.
<16> I can see a slip up of like, auto_ptr< char >(new char [25]) etc
<16> cause that'll probably compile and run, although it's probably doing dubious things
<1> Nah.
<1> At some point, it's likely that an element's going to be copied to be the pivot, and at that point the element in the original sequence will be removed by accident.
<1> There are lots of problems with the way auto_ptr has move semantics written with copy syntax. It enables a lot of code that only makes when copying is used to compile with auto_ptr.
<1> There are some features of the design of auto_ptr to reduce that (the copy ctor doesn't take a const reference), but others which compound it (an rvalue can convert to an auto_ptr_ref.
<1> )
<16> I wish vector has some specialization built in too
<16> like the copy ctor for a T = char should use memcpy
<1> It does, and it's a terrible mistake that we've deprecated. The evil vector<bool>
<16> and not copy ctor each element
<1> jdavis, oh, there's nothing stopping your implementation from doing that.
<1> That's not a problem with vector, it's a problem with your library implementation. Metrowerks library is real big on such refinements; it has specialisations for vector<std::string> and vector<vector> too.
<16> yeah I know
Return to
#c++
or
Go to some related
logs:
#linux
#allnitecafe
#india
#india
suana india -sauna
#allnitecafe
chat appreviations
scramble games bawel dalnet
#php
#india
|
|