![](/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) |
> 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) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Mon, 22 Sep 2008 00:19:04 +0200, Warp <war### [at] tag povray org> wrote:
> 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?
I think it might, but "claims to implement the full standard" is not the
same as "claims to be fully standards-compliant" which of course is not
the same as "is fully standards-compliant".
Strictly speaking, it is impossible to be fully compliant to ISO
14882-1998 since the standard itself contains self-contradictions. I think
most (hopefully all) of those have been dealt with for the upcoming
revision of the standard though.
--
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) |
| ![](/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.
>
> 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.
But it's also "useful" to make the default an ACTIVE breakpoint!
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 wrote:
>> 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?
Or you can enable/disable them by hand while debugging.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |