Thread: template class // normal class

Hello..

Im new to templates (some of you already know that heh) and I wonder if Im right..

In normal class you pass arguments to constructor:

Code:

class somec {
  public:
	somec(char *somearg) { .. }
}

somec *tmp = new somec(arguments);

and in template class you do:

Code:

template <class t, arguments>
class somec {
  public:
	somec(arguments) { .. }
	t data;
};
somec <char> *tmp = new somec<char, arguments>;

Am I right about that? Thanks for help

Your nearly right. The correct code is (green for added, red for deleted)

Code:

template <class t>, arguments>
class somec {
  public:
	somec(arguments) { .. }
	t data;
};
somec <char> *tmp = new somec<char>, arguments>(arguments);

Thanks guys, that made things much easier.. You're great.

Here is the code I have at the moment..

Code:

template <class t>
class datalist {
public:
	datalist(t *init) : data(init) { }
	char *name;
	t *data;
};

int setdata() {
	char *tch = new char[10];
	strcpy(tch, "test");

	int tin = 12;

	datalist <char> *tmp = new datalist<char>(tch);
	printf("data: %s\n", tmp->data);

	return 0;
}

What I want to do is make program figure the type of argument - constructor (tch in that case) so that I could use it for integral tin too.. (without passing <char> if its possible) and then make printf figure out what type of data is it, to print it..

Thanks a lot

Originally Posted by Prelude

>What I want to do is make program figure the type of argument - constructor
>(tch in that case) so that I could use it for integral tin too.. (without passing
><char> if its possible) and then make printf figure out what type of data is it, to print it..
No, on so many levels it would take me weeks to enumerate them all. It sounds like what you really want is a map, and you're going about getting it in the most convoluted and unsafe way imaginable. It's really as simple as this, if I understand what you want to do:

Code:

#include <iostream>
#include <string>
#include <map>

using namespace std;

int main()
{
    map<string, int> m;

    m["test"] = 12; // Pair the value 12 with the key "test"

    cout<< m["test"] <<'\n'; // Print the value paired with the key "test"
}

What I want to do is:

I will have a program input - name with value (many possibillities):
some_var 0,343 -> double
some_var2 some_data -> string
some_var3 353 -> int
some_var4 false -> bool
some_var5 some_data;another_data -> string list

Now I want program to figure what type of data it is, and store it as that kind of data.. Or maybe the better option, hold an array of variable names (lets say some_var should be double) in the program with their type, so that program would automatically know what type of data should variable be.. But I dont have idea how should I do it..

I hope you understand what I mean..

Thanks a lot for your help masters

So there is no 'good' way to solve this problem?

There is another possibility. Perhaps you think you want a variant type, but in reality there is another completely different way to approach the problem. We don't know what your actual situation is, so we can't say one way or the other. You might want to think about your design again. Maybe research some design patterns and see if one of them might fit the bill and give you a way to avoid the need for the variant type.

Originally Posted by Daved

There is another possibility. Perhaps you think you want a variant type, but in reality there is another completely different way to approach the problem. We don't know what your actual situation is, so we can't say one way or the other. You might want to think about your design again. Maybe research some design patterns and see if one of them might fit the bill and give you a way to avoid the need for the variant type.

The only thing why I want to do this is to have program's settings stored in a linked list. I was thinking about using variant types because settings will be strings or numbers and I thought it would be more professional to have variant type for different settings.. So would you recomment me to use string for every setting, and if the setting is number just convert it to int?

Thanks for help once again

Are these settings known at compile time? In most programs I've seen, you know what the settings are when you are writing the program. If you know what the settings are, it is perfectly acceptable to store each setting in its own variable. No list or variant necessary.

If you don't know what these settings will be when you write the program, then how do you know when you should treat them as integers and when you must treat them as strings? How do you tell the difference when you actually use these settings in your code.

Your idea was a good thought, but unfortunately it just isn't the best choice, at least for this language.

The program will have default settings if user wont give them.. I want to store name, type and default option for each setting in an array. So you think it would be smart to use string for each?