comp.lang.c++ Google Group

Re: Is allocating large objects on the stack a good practice?

2010-03-22T01:16:57Z

I believe that you should always allocate on the stack -- if you
can get away with it. Unfortunately, declaring a huge object on the
stack doesn't always work, as there are pre-set stack-size limits.
Fortunately, to do what you want (that is, allocate a large array),
you can use a std::vector, like this:

Re: VS 2005 died on template (part II)

2010-03-21T22:23:58Z

Yes, it is illegal, local types can not be used for template arguments.

Re: VS 2005 died on template (part II)

2010-03-21T22:14:56Z

MS fixed this bug in VC++ 2008.
Compiled OK (not terminated).
I used default compiler settings.
//
James,Am I right - you consider template of local type illegal.
foo(){
typedef struct {} A;
typedef std::vector<A> LocalTypedVector; // is it illegal?
G++ thinks so.

Re: Use static variable across multiple files??

2010-03-21T20:41:13Z

the C++ "static initialization
Just wondering, which GUI framework are you referring to?

Re: invalid conversion

2010-03-21T19:45:21Z

This is basically the exact same error. You are passing node->greater,
which is of type void*, to VertexTextureIndexMatch which is expecting
a VertexTextureIndex*.
Either cast node->greater to the correct type, or change the "greater"
member of VertexTextureIndex to be of the correct type.
While we're at it, that whole function VertexTextureIndexMake() is a

Re: invalid conversion

2010-03-21T15:57:23Z

Thanks Paul now i get three lines before end at:
GLuint greaterIndex =
------
Multiple markers at this line
- invalid conversion from ‘void*’ to
‘OpenGLWaveFrontMaterial::Vert exTextureIndex*’
- initializing argument 1 of ‘static GLuint
OpenGLWaveFrontMaterial::Verte xTextureIndexMatch(OpenGLWaveF rontMaterial::VertexTextureInd ex*,

♬♪♫ ♪ 2010 Cheap wholesale ED Hardy Suit, Baby Suit, Lacoste Suit ect at http://www.rijing-trade.com

2010-03-21T15:15:38Z

Cheap wholesale Suite
Cheap wholesale Baby Suit
Cheap wholesale Puma Suit
Cheap wholesale Adidas Suit
Cheap wholesale ED Hardy Suit
Cheap wholesale Juicy Women Suit
Cheap wholesale Lacoste Man Suit
Cheap wholesale NBA Man Suit
Cheap wholesale Nike Man Suit
More details at website:
[link]

Re: Use static variable across multiple files??

2010-03-21T14:47:46Z

The Singleton Pattern
Google: C++ singleton
[link]
HTH

Re: Use static variable across multiple files??

2010-03-21T14:29:10Z

* SG:
No. The whole point was to have extern linkage for e.g. using functions as
template arguments[1]. You just have a sort of like invisible internal namespace
name like an UUID xxx, as if followed by (after closing of the anon namespace)
using namespace xxx;
Cheers,
- Alf

Re: Use static variable across multiple files??

2010-03-21T14:21:37Z

Isn't internal linkage the default linkage for everything you put in
unnamed namespaces as well? At least this is how I read §7.3.1.1/2:
"The use of the static keyword is deprecated when declaring
objects in a namespace scope (see annex D); the unnamed-
namespace provides a superior alternative."

Re: Use static variable across multiple files??

2010-03-21T14:01:52Z

* James Kanze:
No, ..., and yes.
Re the "no", consider the need to use 'extern' in referencing declarations. And
consider C. Globals are, relatively speaking, technically easy in C.
Consider also the intricacies of global reference type thingies, not to mention,
how const is an array of const? Well I'm sure the standard clarifies this on a

Re: Use static variable across multiple files??

2010-03-21T13:56:49Z

If the variable is defined at namespace scope. What other
lifetime could it conceivably have?
The state of what? There are a few things that should exist for
the entire duration of a program, independently of what the
program does otherwise, but they aren't very frequent. (An
output stream for logging comes to mind, and in some cases,

Re: Use static variable across multiple files??

2010-03-21T13:51:54Z

Except that it doesn't. Variables defined at namespace scope
(like gValue, above) are global by default; his gValue isn't
global because he's explicitly declared it not to be, by using
the keyword static. The only time a variable at namespace scope
is "static" (more correctly, has internal linkage) by default is

Re: new an array of pointers

2010-03-21T13:39:40Z

On Mar 19, 10:31 pm, "Johannes Schaub (litb)" <schaub-johan...@web.de>
wrote:
Good point. I hadn't considered that side of things, but you
(and Comeau) are right: the grammar for [] is
"postfix-expression [ expression ]", and a new expression is not
a postfix-expression.
That's an interesting point. It is obviously (I think)

Re: Assertion vs Exception Handling

2010-03-21T13:19:44Z

Yes. It's a general rule, not an absolute. I violate it myself
in some cases[1]. In practice, I feel that keeping the function
simple and concise is more important. Not that one precludes
the other, but in my experience, if analysing the function isn't
trivial, it's more often because the function is too complicated