| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9
Comments:
<0> i know this isnt C++ related...
<0> but can anyone point me to a nice online 3D modeling guide?
<1> www.gamedev.net
<2> I work at a news site
<0> ow
<0> i work at a electronic manufacturing firm
<2> cool - what kind of electronics?
<0> LED displays
<2> cool - my sons big into stuff like that
<2> son's, I meant
<0> oh ok
<0> nice
<2> I'm into software, hardware isn't my thing... but my oldest is into robots, circuits of all kinds
<2> builds counters for fun, stuff like that
<0> aha
<0> well try doing software without the hardware :)
<2> yeah, I know... but my deployments tend to be on remote servers
<2> so I just wave my hands and say "oh, it's on a set of machines in portsmouth and kansas city, they're really big, I don't worry about stuff too often"
<0> well i just put them together
<0> and curse on the R&D folks because the did it wrong, again :)
<2> hahaha
<0> but it seems that this stunning amount of inefficiency belongs to modern companies
<3> Hello all, I was wondering if someone could help me out here.... for some odd reason my exception handling is not working, was wondering if anyone would be able to look and tell me why;-( Here is my paste: http://rafb.net/paste/results/Vfx8M491.nln.html
<4> sageres there is some overhead to using try/catch... in this case it doesn't matter
<4> but in a more time critical application you shouldn't use it lik ethis... plus you're misusing try/catch
<4> throw exception("i is 0!");
<4> catch(exception ex)
<4> almost typed throw new Exception("...");
<4> too much C# lately
<3> grexican: this is just a sample of my problem... I was trying to through an exception while attempting to instantiate a cl***, and that's when I encountered that problem.
<4> sageres throw string("i is 0!"); ?
<4> you were doing something like that?
<3> oh yes
<3> yes
<4> well does throw exception() work like I suggested?
<4> or string("..."); ?
<3> I'm sorry with exception() getting ican> too much C# lately
<3> bah sorry bad paste
<4> lol what'd you mean to paste
<3> Error_X: no matching function for call to `std::exception::
<3> just one line I htink ok ;-)
<5> sageres: your not throwing a string, you're throwing a char*
<4> wtf is going on with my PC
<4> everytime I open a window it ries a read from my A drive
<4> this is why you don't let your GF touch your PC!
<3> kiwi`: I need to try catching a char* ?
<5> yes
<4> sageres but I still pose the question, why are you doing that?
<3> oh wait
<3> guys between two of you it worked
<3> I did string("whatever exception") and it worked
<4> that's what I told you, fool! heh
<3> i guess I needed to exlicetly specify it was a string
<3> lol thanks grexican
<3> let me ask you a question
<4> [19:08] <4> sageres throw string("i is 0!"); ?
<3> in a much larger program need to try creating a cl*** instance. can I through and catch within the cl*** implemintation ? (don't want the instance to be created if something is wrong)
<4> sageres in the c-tor?
<3> grexican: constructor ;-)
<4> yea, c-tor
<4> c-tors and d-tors should generally not throw... bad practice
<4> it can leave your instance in an unknown state
<4> if you need something like that, protect your c-tor and have a public static method that instantiates the cl*** for you
<4> but even then, meh
<3> grexican: then what is the proper way of refusing instantiation of the lc*** if the bad parameters are p***ed to it?
<4> sageres if bad, set a "bad" flag or something... allow instantiation though
<4> it depends on your requirements really
<6> huh?????
<3> grexican: oh i'm just trying to do a good and proper job ;-)
<6> destructors should NEVER throw
<6> constructors have no other way to say somethign is wrong
<3> vawjrwrk: ok so what is the proper way of letting the program know that the parameters are wrong that are p***ed to the constructor?
<6> an exception
<6> that's exactly how to tell
<7> wrong button :/
<3> vawjrwrk: exception to be "catch"
<7> did you say d-tors can throw exceptiosn vaw?
<6> throw
<3> vawjrwrk inside of the impelmintation of the constructor?
<7> vaw you're saying that it's ok practice to throw in a d-tor?
<6> I said destructors should never throw an exception (that leaves the destructor)
<8> no, they're talking about c-tors
<7> I missed it... I read it then hit the wrong f'ing button
<7> oh ok
<7> *whew* I was gonna sya
<6> I was disagreeing VIOLENT with what grexican wrote
<7> VIOLENTLY* you mean?
<7> I said d-tors hsouldn't throw :/
<3> vawjrwrk: ok constructor can trhough an exception. but catching the exception must also be within the constructor? would it leave constructor in "instantiated" state?
<6> sageres nope
<3> thank you very much guys ;-)
<5> thats why you hit the wrong button
<7> *scratch*
<6> sageres the ONLY way to let the program that's trying to instantiate something that yo0u have a problem is to throw an exception
<6> and have it LEAVE the constructor
<9> but i'm not arabic
<9> i'm a shawy amazigh
<9> heh, what's that cornish talk? :D
<9> yeah of course
<9> i m so glad to learn that
<9> nor kabil
<6> Mmyakkrc stop now
<8> yeah, what the heck?
<9> if u wnat telk in pv im ready
<6> I'm heading home....catch you guys from there
<8> seeya
<3> date
<10> Hello ^_^!
<11> hi!! :D
<10> yay! someone alive!
<3> Hi everyone, have a small question: What is the proper way to terminate a program in c++? ( C abort() and exit() I hear are quite bad for initialized objects...)
<12> let program execution fall back to main and return
<12> that's the proper way.
<3> well unfortunately the requirement of the program states that it has to be terminated directly at subfunction and we can not change the main function in any way... ;-( Is there way way to do it through exception handling?
<12> stab whoever said that
<3> ;-(
<3> what abouts std::terminate() ?
<13> lol
<13> brb need to think about my problem before I ask a q
<3> ok guys, I found the answer. std::terminate() terminates the program in the proper way by shutting down all handlers that should be shut down.
<13> gj, now for my problem, is there a way to take the changes to all of my controls in my dialog box and handle them in the same handler?
<12> what handler
<13> for mfc dialog controls
<12> what handler
<13> 1 sec
<13> the Edit Box message is EN_CHANGE which is handled by void CCEdit::OnChangeLname()
<12> I still fail to see what you're asking for
<13> I want to handle all of my messages with one handler
<13> my problem is, I have a time AM PM droplist, and also time begin and time end edit boxes, and I want to know if they changed the time of day also if they changed the AM/PM
<12> look up the ON_CONTROL_RANGE macro
<13> doesn't look good
<13> my weird Idea was to send the changes back to before I turn everything into objects like, Name of Person, and Colord rectangles that show the info
<13> but even then I would still have to know if all of the messages have been handled
<13> I can't just flip the AM/PM and not know if they are changing more than that
<12> I still don't know what you're trying to do
<12> this is making very little sense
<13> ok sorry lemie explain
<14> it seems now would be a good time to buy google stock if one has money
<12> I'm not investing yet
<13> I created an excel-like program which shows times/names/more nfo about the cl***es going on in each room at my comp labs at work, I converted the 1450 hours begin lets say to 2 hours 30 minutes in the PM, now if I handle just the AM/PM combo box without knowing about the other changes to the time, I won't be able to re-calculate the size of the rectangles( hours ) the cl***es are
<13> the hours begin and end are just colored rectangles
<13> I can invest
<13> how much per share?
<12> I'm off to bed
Return to
#c++
or
Go to some related
logs:
my walmart executable error
#MissKitten
#mirc
#AllNiteCafe
houseman mirc
#linux
#c++
nasm relocation truncated to fit: R_386_16 against `.text'
#linux
#javascript
|
|