Happy New Year

[Josh @ Dreamland]

Yes, but I wanted them to be able to say
map a;
And have it assume they meant map<variant, variant>.

This whole idea started when Luda bitched he wanted structs in EDL.
It's perfect, when you think about it. GM users have an inefficient way of having a structure (global, and instantiations of bloated-down objects), which Luda has apparently exploited in the past. This way will allow users, any who are willing to read a 150 word manual entry, to declare a structure as efficient as any other.

Also, parsing STL for members removes ambiguity.
string a;
a.length()... that won't even look like a syntax error, because length is a public member of a's type, string.

[RetroX]

By the way, Josh, make sure that your handler doesn't see template<template<>> as the same thing as template<template<> >, although, I'm pretty sure that you've already handled that.

[score_under]

template<template<>>
template<template<> >

Are those actually different? Whitespace is not supposed to matter very much in C-based languages.

[luiscubal]

Yes, they are. Because whitespace DOES matter in C.

== is not the same as = =.
And >> is an operator(bitwise shift), so it is forbidden in templates.
That is, it WAS forbidden until C++0x came.

[RetroX]

template<template<>>
template<template<> >

Are those actually different? Whitespace is not supposed to matter very much in C-based languages.

>> is considered as an operator, so they must be separate.

[score_under]

template<template<>>
template<template<> >

Are those actually different? Whitespace is not supposed to matter very much in C-based languages.

>> is considered as an operator, so they must be separate.

I see, *adds to list of reasons not to use C++*

[Rusky]

It just comes from the stupid idea to use <> for templates. Because the lexer finds the biggest token it can and >> is an operator, closing two template tags in a row causes problems. Other than that, this behavior for the lexer makes perfect sense- it parses "asdfasdf = 3" as asdfasdf, = and 3, rather than a, s, d, f, a, s, d, f, = and 3.

[score_under]

It just comes from the stupid idea to use <> for templates.

Exactly.

Because the lexer finds the biggest token it can and >> is an operator, closing two template tags in a row causes problems. Other than that, this behavior for the lexer makes perfect sense- it parses "asdfasdf = 3" as asdfasdf, = and 3, rather than a, s, d, f, a, s, d, f, = and 3.

And if it did that (string into array of chars, i.e. NOTHING :p ), there'd really be no point in it.

[RetroX]

It just comes from the stupid idea to use <> for templates. Because the lexer finds the biggest token it can and >> is an operator, closing two template tags in a row causes problems. Other than that, this behavior for the lexer makes perfect sense- it parses "asdfasdf = 3" as asdfasdf, = and 3, rather than a, s, d, f, a, s, d, f, = and 3.

It does not make sense to be green without chlorophyll.

[luiscubal]

D uses f!(1) instead of f<1> for templates.
C# and Java solve this problem making templates apply only to types, never numbers, so you won't ever write class X<3>>2>.

[RetroX]

D uses f!(1) instead of f<1> for templates.

Good for D.

C# and Java solve this problem making templates apply only to types, never numbers, so you won't ever write class X<3>>2>.

Which is one of the reasons that C# and Java suck.  Number templates are extremely useful in some cases.

[Josh @ Dreamland]

Like fucking up my parser. Twice.

[Micah]

C# and Java solve this problem making templates apply only to types, never numbers, so you won't ever write class X<3>>2>.

Which is one of the reasons that C# and Java suck.  Number templates are extremely useful in some cases.

Well, C# and Java don't really have templates if I'm not mistaken; they just have runtime generics, and with runtime generics it only really makes sense to have type arguments, doesn't it?

[luiscubal]

Yes, they are called generics in C# and Java.
Now, C# has generics on the runtime. Java doesn't even have that. Generics are a compile-time trick. They are erased from the binary. Which is the number 1 problem with Java generics.
As for C#, I don't see how numeric generics could be used but, then again, I don't see what they're for in C++ either.

[Rusky]

In C++ you can make statically-allocated containers of varying sizes:

Code: [Select]

template <typename Value, int size>
class Stack {
private:
    Value value[size];
public:
    ...
};