| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11
Comments:
<0> anyone want to correct me on that?
<0> I'm actually not sure about teh char arr[] version?
<1> so that often depends on the type of the array, right?
<0> AvihooI, no.
<0> The 2nd one will work no matter what the type.
<0> BUT
<0> it's gotta be declared right there
<0> you can't p*** it around as a pointer
<0> and expect that to work.
<0> sizeof(int *) == 4
<1> ohh, so it has to be in the same block?
<2> AvihooI pretty much, yeah
<2> why are you using an array anyhow?
<3> i'm willing to paypal someone if they can help me out with this..
<1> vawjrwrk, school homework, we don't use anything else
<4> joe-f what's the question?
<3> i need to debug this binary
<0> http://www.foxnews.com/story/0,2933,186876,00.html
<0> ugh
<4> then learn how to do it, that's the point
<3> i need to find out what strings to enter
<0> Why do we let them in to public schools to begin with?
<4> the teacher doesn't give a **** if you can pay someone to do it - the task is there so you can learn how to do it yourself
<2> AvihooI is this a C++ course you're taking?
<3> i dont want someone to simply do it, i need help with understanding it
<1> kinda, computer science in high-school, we learn C... but actually use C++ compiler
<0> ahhhh
<1> a C++ compiler*
<2> AvihooI sorry to hear that
<0> well, then AvihooI
<0> sizeof is all you've got
<2> C++ is a MUCH better language
<0> if you're going to p*** it around as a pointer
<0> you've gotta p*** the bounds with it too.
<5> why the hell is RICHEDIT ignoring my EM_SETUNDOLIMIT message?
<0> Some states were favoring illegal immigrants over citizens in college admissions?
<0> WTF?!?
<1> NoideaWRK, yeah, that's what they told us to do, thought there might be a way to do it without p***ing the bounds
<0> OOP AvihooI
<0> that's the way to do it
<0> you can do OOP in C
<0> it's just not as pretty.
<5> or you could just use C++ :)
<5> it is what it's there for
<0> no
<0> he's in a C cl***.
<2> he should be in #C then
<5> ah yes, missed that
<6> howdy!
<1> we'll learn C++ actually... I mean, object oriented programming proper
<6> Got a quick question
<1> anyway, thanks for the help
<6> I'm brain dead on the syntax for ShellExecute in c++
<7> people, where does exception design stop? I am finding myself overwhelmed by exceptions. For example, I have a HardwareException, from this Hardware exception I derive a OpenPortException, then what? should I derive an exception for every reason why the port failed to open?
<6> I am not a big fan of calling a 3rd party program but i'm sorta in a jam unless someone knows of a library I missed >.<
<6> I'm writing this program for our multimedia whiteboards that have webservers to pull down html files parse them for pdfs and save them in a designated file structure on our server
<0> mozai
<0> that's up to you.
<6> Basically the idiots who built these boards didn't provide windows file sharing (even though they run CE) and also didn't think FTP access would be a good idea.
<0> design decisions :)
<6> The internal drive space on the boards is finite (obviously) so I'm pulling them off using wget for win32
<0> I personally tend to do something more like 1 exception cl*** per major block of the program
<6> Mostly I want to find the idiots who made these $14,000 whiteboards and take them outside on the playground after school is over >.<
<0> I can stuff as much info into an exception cl*** as I want
<0> I try to keep their interfaces consistent
<7> Noidea: Yes, all the expcetions inherit from an exception cl***
<0> hopefully std::exception
<7> no :-/
<6> Anyhow so I just want to call wget from within my program and I am feeling retarded because I think it's shellexcute? but do i need includes for that and what is the syntax - ty in advance!
<0> In my opinion
<0> all exception cl***es should start at std::exception
<0> then I have 1 handler around main to catch std::exception
<0> and ...
<0> and handle them identically
<0> err
<0> handle all uncaught exceptions identically
<7> i see...makes sens...
<7> I wanted to make only a Hardware Exception, and an error code inside the excpetion
<0> Like I said
<0> that's a design decision
<0> it's really a question of will they be handled differently
<7> OK, so it wouldn't be considered a 'bad design' if I do so
<0> will people tend to care that it was one type over another
<0> and, how much overhead in maintenance are you creating by adding lots of different exception cl***es
<0> as opposed to just 1
<7> yes, that is it...Immagine creating an excpetion cl*** for evey possible failure
<7> it would be a nightmare
<0> yup
<0> I've been through this whole thing before myself.
<0> I like exceptions
<0> but, you start looking at the overhead of creating a new cl*** for every error tha tmight happen
<7> yes, they are very neat, but then when do you stop creating them...
<0> I do 1 per major software block
<0> if they'll get handled the same way basically
<0> they're the same in my mind
<0> Like, there may be tons of different ways my object may fail
<0> but, to the user
<0> it failed is all they really care about
<0> and, knowing which module failed
<7> true.
<0> tends to be the thing that counts
<0> You tend to have situations where 1 module calls into several others
<7> do you somehow automate module failure, or do you type in the string yourself? ( "mycl***::mymethod().Failed file format)
<0> and you know how each of those calls can fail
<0> but, you need to know which failed of the several
<0> so as long as each major module is throwing a different type
<0> that's good enough
<0> anyway
<0> automate module failure?
<0> it depends
<0> I've used macros to generate the fail strings before
<7> and now?
<0> but, it depends on the type of errors I'm throwing
<0> errors to a user
<0> they don't want line numbers and source file names typically
<0> they just want an error message
<0> and, I've found that line number/file name doesn't tend to tell me much more as a developer anyway
<0> I can usually grep for the message and find where it failed
<0> or, even better
<0> in my debug build
<0> I remove the try/catch block in main
<0> so all unhandled exceptions cause a crash
<7> Oh
<0> then, I just fire up gdb
<0> it'll take me right to the throw
<0> and I've got the full state of what was going on when it did the throw.
<7> not bad at all
<0> saves me a debugging step of opening it up, setting the break point, and starting over.
<0> ok, well, have fun with that, it's lunch time for me.
<7> thanks sir
<7> that was very helpfull
<8> anyone can help me about one question in C#?
<0> no problem.
<8> ok
<6> lol
<6> any help on the spam i posted up a bit?
<9> sounds like a Windows problem
<6> I just wanna know syntax to call a 3rd party program
<6> is it ShellExecute? and do I need to include something specific for that function?
<8> i am new user of OOP...in this case...C#. I have to develop a soft who listens through UDP for frames... and i have to open more than one "Form"...so how can I listen when i am in another form (cl***)? I have an event for UDP frame received... Can anyone help me plz?
<9> std::system("path-to-exe");
<9> luigi27: did you try #c#?
<9> jill_s: ShellExecute is probably some Windows function.
<6> ah okies
<6> ty sorry to bother
<8> can't get into c#...there is nobody.
<9> what?
<9> I see 50 people in #c#
<1> that's because he said "C#?" and not "C#"
Return to
#c++
or
Go to some related
logs:
#php
.roma.itly
#MissKitten
#AllNiteCafe
What is the modern day name of what the Romans called Aquae Sulis
#MissKitten
badi nikik
masculine pee
i like satin panties
#AllNiteCafe
|
|