![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>I just installed Micro$oft Visual C++ 2008 Experss Edition.
>
> My God... what have I done?? O_O
You'll figure it out. =) It's handy once you do. Learn the keyboard
shortcuts and you'll be able to iterate on your code very quickly.
And it will give you compile errors when you don't return something from a
function with a return type. =)
- Slime
[ http://www.slimeland.com/ ]
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Slime wrote:
>> I clicked on the big shiny button that says "toggle breakpoint". It looks
>> like a big grey square, and sure enough, when you click it, a big grey
>> square appears at that line of the source code. Only by accident did I
>> discover that you have to click on this breakpoint to make a big red dot
>> appear on it, and *then* it will do something. (It is unclear to me what
>> the hell use an inactive breakpoint is, but still...)
>
> Odd. You can also just press F9 to make a breakpoint.
Yeah, well, once you *know* that it's easy enough. ;-)
> Inactive breakpoints are usually useful when you've added a complicated
> condition to a breakpoint and you want to turn it off but get it back later.
Wait - you can have conditional breakpoints?
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> My God... what have I done?? O_O
>
> You'll figure it out. =) It's handy once you do. Learn the keyboard
> shortcuts and you'll be able to iterate on your code very quickly.
It'll never be quite as easy as in interpretted compiled language, but
what can you do? This is what people use, apparently...
> And it will give you compile errors when you don't return something from a
> function with a return type. =)
Heh. Pity it won't warn me when I do any of the 50,000 other dubious
things that are legal in C++. :-S
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> Yeah, well, once you *know* that it's easy enough. ;-)
That's what we're here for =)
It's also worth looking through the menus for shortcuts to common operations
like compiling and executing.
> Wait - you can have conditional breakpoints?
Yeah. In the version I use at work, you just right click on the breakpoint
and select "condition". In previous versions it was in a submenu of the
right click menu. I wouldn't be surprised if this is one of the removed
features from the express edition. (If it's free, they had to take
*something* out.)
- Slime
[ http://www.slimeland.com/ ]
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Orchid XP v8" <voi### [at] dev null> wrote in message
news:48d6aa2d$1@news.povray.org...
> Wait - you can have conditional breakpoints?
>
Yup. Have had for a couple versions of visual studio. Very handy for when
you want to break on the 99th iteration of a 1..100 loop, or for when you're
sure a variable should have a value within a certain range at a certain
point, but very occasionally doesn't.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Slime" <fak### [at] email address> wrote in message
news:48d6a77b@news.povray.org...
>> According to "Thinking in C++", you can use the keywords "and", "or" and
>> "not" in place of symbols. GCC accepts this. However, Visual C++ doesn't
>> seem to like it.
>
> Ewww, someone got Visual Basic in my C++.
RotFL
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Slime <fak### [at] email address> wrote:
> I haven't used the Express edition, but what I normally do is go to
> Project -> Add New Item, which creates a file *and* adds it to the current
> project.
I usually create a new source file with emacs and then select
Project -> Add existing item.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Fredrik Eriksson <fe79}--at--{yahoo}--dot--{com> wrote:
> The bitwise operators are all single character. There are also only four
> of them. You get used to it.
<< and >> are bitwise operators, and are longer than a single character.
Not to talk about ^=, |=, &=, <<= and >>=.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Fredrik Eriksson <fe79}--at--{yahoo}--dot--{com> wrote:
> There is currently as far as I know only one C++ compiler vendor that even
> claims to implement the full standard.
Does the count change if we disregard export templates?
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Mon, 22 Sep 2008 00:16:19 +0200, Warp <war### [at] tag povray org> wrote:
> << and >> are bitwise operators, and are longer than a single
> character.
True, though they have no logical counterparts.
> Not to talk about ^=, |=, &=, <<= and >>=.
Also true, but I would consider those a kind of compound operators.
--
FE
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |