What we do:
First, a doc in which we essentially lay down the use cases. This doc usually starts with a dictionary, containing terms specific to the business domain, terms coined during discussions with the customer, terms which are more technical in nature but which the customer has to learn in order the communication to work properly. Then comes a list of unstructured, non-functional requirements. These are things like number of...
Aflj
Last Activity: Oct 28 '07, 02:34 PM
Joined: May 25 '07
Location:
-
It's a long time since I last touched MS-specific technologies, but if I correctly remember, you can use VBScript (which is sort of a VB) to script web pages, if you (or your users) are using only IE for browsing. Also, you should be able to use JS for server-side scripting.
Even more, using MS's client-side scripting technologies, you should be able to build apps scripted in JS similar to those you can do in VB, by scripting similar...Leave a comment:
-
Finally! Thanks a lot.
To summarize my understanding of the problem: due to implicit conversions provided by C++, if this hiding mechanism wasn't in place, small changes in a base class, of which the compiler won't even warn, can determine changes in the behavior of derived classes. Am I right?...Leave a comment:
-
:o(
Still no answer to my initial question, or I am stupid.
To repeat myself, if you have:
[CODE=cpp]class C1
{
public:
void f1()
}
class C2: public C1
{
public:
void f1(int);
}[/CODE]
then:
[CODE=cpp]C2 c;
c.f1()[/CODE]
won't compile. This is normal, and happens because in C++ each class defines...Leave a comment:
-
Right. But more often I want to derive a WoodenDoor or an IronDoor, and besides inheriting the open() method, also add an open(int sqeakLevel). Instead of this happening automatically, I have to explicitly state this.
On the other hand, if I have written both the Door and the MagicDoor classes, and somebody else has written a Robot class, which has a method openDoor(Door* pDoor), and I pass it a MagicDoor*, it will open the MagicDoor...Leave a comment:
-
implicit hiding of same-named methods of base class in derived classes - why?
This code won't compile (two compilers tried, gcc and VC++, both of recent versions, but I don't remember them exactly):
[CODE=cpp]class C1
{
public:
void M1(int i) {}
};
class C2: public C1
{
public:
// using C1::M1;
void M1(int i, int j) {}
};
int main(int argc, char *argv[])
{
C2 c;
c.M1(14);
...
No activity results to display
Leave a comment: