| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9
Comments:
<0> cn28h, stringstream does not have empty() ?
<1> I don't think it does
<1> could be wrong
<0> well thats a kick in the face if it don't
<2> it's a stream
<0> although, ya
<0> I guess non of the streams do
<2> just check if(stream) to see if you're at the end
<1> and if there is no input waiting it will be false?
<2> er
<2> check the result of the read operation, like any other stream
<1> can I push back onto the stream?
<1> hm
<1> maybe I don't need to
<2> a stringstream is both an input and output stream
<2> you can write to the end of it, yes
<1> yes, but I meant an unput operation
<0> you can normally redo your logic so you don't need an explicit empty check
<2> unput?
<1> yes
<2> heh
<0> instead, while (stream >> var) { stream is good }
<2> you mean you want to peek first
<1> oh, that sounds like a good idea
<2> what for?
<1> the peek()
<2> why do you need to peek?
<1> to see if there is data waiting, if there is it will be read, if not the data is read from elsewhere
<1> but I suppose it can easily be done by just trying to read it
<1> and if it fails
<1> just have to make sure I reset the error flags with clear()
<2> if( stream >> data ){ ..read success.. } else { ..read from somewhere else.. } ..process it..
<1> right
<3> which one will be calculated first - or %?
<0> who knows... I wouls ***ume %... but parenthesis are your friend
<3> tnx
<4> 0xa0
<5> javaq_ has no friends
<4> %
<4> ./*% priority on -+
<3> toast: thank
<4> but u have no friends still
<6> hey guys. not C++, but still, maybe someone may help me with the old pascal. for some reason after setting p:=nil; p still points to the place where it used to. why could it be ?
<2> #pascal
<3> why pascal?
<6> #pascal does not exist, unfortunately.
<7> calc fallback
<8> fallback = We are NOT your fallback channel. If you can't get help somewhere else (not related to C++) you won't get it here. If you keep going with this, chances are you'll get your *** booted.
<9> does the pixel width and height differ?
<7> Sheesh
<9> 'And Related Development'
<7> Besides that having nothing to do with C++... on what OS? What monitor? What video card? What resolution? What form factor?
<7> And pixels aren't related.
<9> typically speaking
<9> if i may argue, graphics programming is surely related to c++ programming, and in graphics programming pixel width/height is related info
<2> what's the problem?
<7> You can write anything in C++ (since it's Turing complete), but that doesn't make all problem domains C++ related.
<7> rdragon's a pixel-head, so he gets off on this stuff.
<2> hehe
<9> lol
<2> you're wondering if pixel width and height are ever different?
<9> i just want to know if typically speaking pixel width and height differ or not
<2> i don't know of any case that it does, but I suppose it could
<9> oic, so typically they are the same
<7> "typical" is defined by where your pixels are displayed.
<9> typical meaning generally speaking, and not on a particular display
<7> Stop and consider for a moment all the different possible displays, and consider the meaning of "typical" in that context.
<2> well, we could run around hypothetical situations all day, but how about saying what you're REALLY trying to do, and what the problem is?
<9> i want to confirm pixel width/height are same in physical dimensions because i'm trying to have a ratio of pixelsPerMeter which doesn't depend on x-axis or y-axis
<9> on a typical windows system (laptop and pc)
<7> You have to ask the system. There's a Win32 API for that.
<7> (Because there's no "typical")
<7> GetSystemMetrics
<7> And, lo and behold, we still haven't talked about anything having to do with C++.
<7> Fortunately for you, I'm in a *good* mood.
<2> http://www.lurkertech.com/lg/pixelaspect.html
<9> thx
<2> search google for 'pixel aspect'
<9> k
<7> Man, Vista's new Windows-Tab is cool.
<4> to use List<>
<2> what?
<4> do you need to have a default constructor ?
<2> what the hell is List<> ?
<4> in the stl
<2> no such thing
<7> You mean std::list
<4> #include<list>
<2> it's std::list
<7> And no, you don't. But it's a good idea.
<4> c:\program files\microsoft visual studio 8\vc\include\list(441) : error C2512: 'Transaction::Transaction' : no appropriate default constructor available
<2> well if you resize() it, I'm pretty sure you'd need one
<7> true
<4> why do i get this err0r
<7> toast, it would help to see the code
<2> you're probably doing something to the list that requires that you need a default constructor
<7> The source base I'm working on now is MFC written by C coders.
<7> I'm hating life. A lot.
<2> yuck :/
<7> I started a page on my intranet Wiki on "Things to Fix in <product>"
<7> And I'm pulling no punches.
<2> yeah, good
<7> My favorite so far...
<7> CString foo; foo.Empty();
<2> ...
<7> There's a good WTF.
<2> yeah
<2> some people are just way too insecure, heh
<4> http://pastebin.com/595745
<4> very simple code, just testing..
<2> i'm on the virge of a new job... can't wait, I think (hopefully I won't also hate life once I see the code)
<2> going to Seattle (well, redmond) on tuesday/wednesday next week
<2> yeah there you go
<2> line 14
<7> I don't understand how so many crappy coders are writing so much of the code in production.
<2> you certainly need a default constructor - how else is it going to create 30 Transaction objects?
<2> also toast, main() returns int
<7> int main() {} // This works, and it's one fewer character than void
<2> and why in hell are you casting i to a char?
<2> why not just make it a char to begin with?
<2> you're also using that weird c function-style cast
<2> you're also using the brace style I don't like :/
<4> return 0; is 7 more char ;p
<2> no toast
<2> return 0; is implicit at the end of main()
<7> characters 0 through 30 aren't terribly meaningful, either.
<2> void main is *incorrect*
<7> toast, you don't have to type the return line.
<2> it isn't and never was valid C++ OR C
<7> int main() {} // this is correct, and returns 0
<4> k ;)
<7> void main() {} // this is incorrect, so don't bother
<4> i ujst do a cin>> somthing; normally
<4> k chief
<4> http://pastebin.com/595779
<4> e:\hierapoly\hierapoly\foo.cpp(20) : error C2679: binary '!=' : no operator found which takes a right-hand operand of type 'std::list<_Ty>::_Iterator<_Secure_validation>' (or there is no acceptable conversion)
<4> with
<4> ops nevermind
<10> Well, this is a decidedly peculiar Battlestar Galactica episode
<11> hey
<11> i have a question about inheritance
<11> if i have an array of a supercl***
<11> (which holds various subcl***es) and i call the toString method of one of the items in that array, will it call the toString method from the super or the subcl***?
<12> Are base cl***es usually more specific than derived cl***es?
<11> no
<11> other way around
<13> yeah
<13> dirived is more spec
Return to
#c++
or
Go to some related
logs:
#c
#linux
#linuxhelp
linuxthreads + nptlonly gentoo perl
Niger Noger
PUSSY FACKERS
weighs 5,500 billion billion tons
#linux
#squid
#linux
|
|