Okay... I'm using Visual Studio 2010. It has a few bugs but whatever.
How do I make a test, not to see if everything works. I am trying to mae it so I can use the tool and see if it works properly and everything... Thanks!
Printable View
Okay... I'm using Visual Studio 2010. It has a few bugs but whatever.
How do I make a test, not to see if everything works. I am trying to mae it so I can use the tool and see if it works properly and everything... Thanks!
Just a guess based on previous versions (and assuming you're using standard C++), but try creating a Win32 Console Application project, and check the Empty Project box. Then create a single cpp file in that project and paste the following code:Find the command to build, does it build? Find the command to run (or execute), does it run?Code:#include <iostream>
int main()
{
std::cout << "Success.\n";
std::cout << "Press enter to exit.\n";
std::cin.get();
}
It should work as previous versions, only the C++ Directories is gone. I have complained about that.
A word of warning, however: this versions is buggy and slow. Very slow. Use at your own risk.
Write the following and see if it compiles this time, as it should:
Or try the following and see if the compiler finally generates a C4430 error because the friend declaration does not name the return type.Code:class foo {
public:
void bar();
};
void foo::foo::bar() { return; }
int main() { }
The first I was discussing recently somewhere else. Everyone seemed to think it was correct behavior to generate a compile time error. However:Code:class foo;
class bar {
public:
bar(int x): value(x) {}
inline int sum(foo &obj);
private:
int value;
};
class foo {
public:
foo(int x): val(x) {}
friend bar::sum(foo&);
private:
int val;
};
inline int bar::sum(foo &obj) {
return obj.val + value;
}
And...Quote:
Originally Posted by ISO-IEC 14882-2003(E), §9.2 Classes (pag.153)
The second one is an old issue. Probably something to do with how C++ 6.0 used int as the default type.Quote:
Originally Posted by ISO-IEC 14882-2003(E), §3.4-3 Name Lookup (pag.29)
It's still in beta, which is real beta, not video game beta. You shouldn't be using it unless you already have experience with the product line. I suggest you use Visual Studio 2008 Express, which is also available for free.
What does "real beta" mean?
Video games typically use 'beta' as a marketing ploy.Quote:
Originally Posted by Elysia
In ye olde days software (and hardware) went through 3 stages.
Alpha - Internal development, incomplete, functionally limited, and generally not stable enough for consistent use. This was everything from the first line of code until the software entered Beta.
Beta - All the major features are present and production has shifted to debugging, compatability issues, and interface design. The product usually still has major or minor stability issues.
Gamma (modern usage is Release Candidate) - Release. Bug fixes, but little if any further development takes place.
Many business customers, particularly for engineering software pressured developers to let them get a pre-release copy of software that was still in beta, generally this was not an issue because engineers tend to be much more forgiving and adaptable to buggy software (after all its still in beta) and they could provide valuable qualified feedback regarding undiscovered bugs. The general public got the notion into heir head that beta was getting a 'sneak peak' at the software and video games in particular have taken advantage of that with faux beta programs that are really just pre-release marketing campaigns.
Microsoft's betas aren't using this strategy, though. They are more like milestones than betas, if you ask me.
Still, that makes it all the more reason to use at your own risk, because they are buggy (although, they are not Alphas).
Actually MS Betas are closer tot he traditional sense of bet6a than to the marketing idea of beta.Quote:
Originally Posted by Elysia
Software release life cycle - Wikipedia, the free encyclopedia
Argh. These terms have become so complicated now that they mean nothing.
A beta can or can not be a work in progress build.
A release candidate may or may not mean a feature complete product.
Take nothing for given.
Anyway, Microsoft's VS10 build is not feature complete and it's rather unstable. Let's not nickname it.
I agree, this is what happens when laymen try to be computer literate not to understand it but to sound cool.Quote:
Originally Posted by Elysia
I already nicknamed it, but vBulletin keeps turning the nickname into pages and pages of asterisk's.Quote:
Anyway, Microsoft's VS10 build is not feature complete and it's rather unstable. Let's not nickname it.
You mean like trying to differentiate between beta and real beta? I agree. It's what happens when they try to do it.Quote:
Originally Posted by abachler
That might hurt if I actually had any respect for your opinion.Quote:
Originally Posted by Mario F.
Don't worry. You only fool yourself.
No arguments please...
Anyway, the point being that the discussion of the term "beta" should be left for academics with little code in their hands and lots of time for talking. In common usage a beta is a beta is a beta. And it's not a final product. There's no science to it.
And it has nothing to do how computer literate someone is. The notion itself only reveals contempt and is only proper on someone who just insists in putting themselves above everyone else.
...
As for the original question, I can only assume the OP knows perfectly well this is a beta product and is asking how he should test its functionality.
1. First, do as Daved suggests and write a simple program
2. Next, try to see if some bugs from the previous versions still exist (two of them can be found on post 4)
3. You can also, read about the new functionalities and try to use some of them.
4. and, search for blogs, articles and reviews on google.