Original Post
#include <iostream> // Just watch what happens
🔒 Locked
Uh Oh....
Advertisement
nav@seeker:~/pp/work$ echo "#include <iostream>" > test.cpp
nav@seeker:~/pp/work$ g++ -Wall -c test.cpp
nav@seeker:~/pp/work$
There''s nothing wrong with that for me. So, what''s this problem you''re seeing?
quote:
Original post by elis-cool
What happened???
CEO Plunder Studios
Everything after is green...
EDIT: Nooo, don't actually TEST the code...the problem is in the post - when i post that, everything in the post is green. It might not work with Mozilla (if that's what your using)
_____________________________________________________
ICQ #: 149510932
Google - OpenGL - DirectX - Windows Guide Network - MSDN - Symantec Virus Info
"Imagination is more important than knowledge." - Albert Einstein
[edited by - Programmer One on April 10, 2002 11:21:22 PM]
quote:
Original post by Programmer One
EDIT: Nooo, don''t actually TEST the code...
Heh, okay.
quote:
Original post by Programmer One
Everything after is green...
quote:
Original post by Programmer One
It might not work with Mozilla (if that''s what your using)
Yes, I see the green text in Mozilla.
How about I try it too...
Edit: I dont think it worked...
CEO Plunder Studios
[edited by - elis-cool on April 13, 2002 7:28:03 AM]
#include <iostream> // Edit: mybe ya gotta do comments
Edit: I dont think it worked...
CEO Plunder Studios
[edited by - elis-cool on April 13, 2002 7:28:03 AM]
K it worked after I edited, so you either have to edit or have comments... so dave are you going to fix this bug?
CEO Plunder Studios
CEO Plunder Studios
<font color="green">#include <dummie.h>
<font color="gray">//sss
</font>
[/code]
</div>
<!--ENDSCRIPT-->
<BR>
<BR>Test.
<BR>
<BR>
There is the problem. When you include the comment, the color is changed to gray *without first closing the green font*. Then, after the gray, the software includes a /font to go back, but because the gray font was inside the green font, and there isn't a /font for the green font, all the rest is green.
[edited by - Ronin_54 on April 13, 2002 7:39:52 AM]
[edited by - Ronin_54 on April 13, 2002 7:40:40 AM]
quote:Nope.
Original post by elis-cool
so dave are you going to fix this bug?
quote:
Original post by Myopic Rhino
Nope.
? Kind of an odd answer, especially after ronin broke down and identified the problem so thoroughly...
____________________________________________________________
Direct3D vs. OpenGL
quote:
Original post by Promit
? Kind of an odd answer, especially after ronin broke down and identified the problem so thoroughly...
The new version of the forums are coming soon (or so they claim), so there really isn''t much of a reason to bother with it.
quote:I "broke down and identified the problem" myself when I first saw this 4 days ago. I also saw that fixing it was going to require more effort than I was willing to expend, considering (1) it doesn''t come up that often, and (2) the new forums already handle this correctly.
Original post by Promit
? Kind of an odd answer, especially after ronin broke down and identified the problem so thoroughly...
Any ideas as to when the new forums will be active?
John B
John B
quote:
Original post by Myopic Rhino
I "broke down and identified the problem" myself when I first saw this 4 days ago. I also saw that fixing it was going to require more effort than I was willing to expend, considering (1) it doesn''t come up that often, and (2) the new forums already handle this correctly.
Good enough.
So about the new forums... what exactly is going to be different about them? I mean I hope you dont change the look too much as I have grown to like it and gotten very used to it, and as we all know, no one likes change
CEO Plunder Studios
CEO Plunder Studios
The looks won''t really change. The changes we''re focusing on are improved usablility, better performance, anti-abuse measures, enhanched user profiles, etc.
Topic Locked
This topic has been locked by a moderator. New replies are not allowed.
Sign in to reply to this topic.
Advertisement