Why Console class is a sealed class?
352070
System\n\nThe Console class provides basic input and output support for applications that read from and write characters to the console. If the console does not exist, as in a GUI application, writing to the console produces no result, and no exception is raised.\nThe standard input, output, and error streams are represented by properties, and are automatically associated with the console when the application starts. Applications can redirect these properties to other streams; for example, streams associated with files instead of the console. [Note: For additional information see the System.Console.SetIn(System.IO.TextReader), System.Console.SetOut(System.IO.TextWriter), and System.Console.SetError(System.IO.TextWriter) methods.]\n\nBy default, the read methods in this class use the standard input stream and the write methods use the standard output stream.
193431
Probably because the constructor doesn't accept objects as arguments. Just a guess, though.
269292
You can try it via an IDE......... but in the end that also uses the Java Virtual Machine to launch it ... You can't escape it as it is a core component of running Java
643784
because "CON" is a reserved word in DOS. It means the console.\n\nGreat discovery! my 2 cents to you! :)
1035309
I am not sure sir\nremember that the open gl uses in first\n\nUsing namespace std;\n\ni have a version of turbo c that give me errors when this line is entered if si then just delete this line ( '.__.')
109898
Another tip - class names and file names are CASE SENSITIVE.  If you create a class "Apple", and refer to it as "apple", you won't find it at runtime.\n\n(I'm just beyond a novice at Java - hope this helps too - just vote for the other guy).
1046588
i dont see why we need this dam class!\nim not trying to be no computer tech! ;)
933539
What do you mean by java class?
249182
Final just means that the method (or variable) it refers to cannot be modified on s subclass. It is actually redundant on a static anyway because statics are never part of an oject instance.
293992
Use TOBA (see link below)\n\nToba translates Java class files into C source code. This allows the construction of directly executable programs that avoid the overhead of interpretation.
657742
Not worth the effort — encapsulation is for code, not people. \n\nIt doesn't violate encapsulation for a programmer to see the private and/or protected parts of your class, so long as they don't write code that somehow depends on what they saw. In other words, encapsulation doesn't prevent people from knowing about the inside of a class; it prevents the code they write from becoming dependent on the insides of the class. Your company doesn't have to pay a "maintenance cost" to maintain the gray matter between your ears; but it does have to pay a maintenance cost to maintain the code that comes out of your finger tips. What you know as a person doesn't increase maintenance cost, provided the code you write depends on the interface rather than the implementation. \n\nBesides, this is rarely if ever a problem. I don't know any programmers who have intentionally tried to access the private parts of a class. "My recommendation in such cases would be to change the programmer, not the code" [James Kanze; used with permission].
3150
The basic problem is that CON is the built in name used for a standard I/O port representing "console". This is just like other ports, like LPT1, LPT2, COM1, COM2, etc. If you managed to created such a file/folder on your machine, all normal input and output that normally come from the keyboard and display on the screen would have to come from and go to the file/folder you created.\n\nDOS device names are reserved words, and cannot be\nused as folder or file names. When parsing a reference to a file or folder, Windows correctly checks for the case in which a single DOS device name is used in the path, and treats it as invalid.\n\nfollowing are reserved device names\n\nCON, PRN, AUX, CLOCK$, NUL, COM1, COM2, COM3, COM4,\nCOM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4,LPT5, LPT6, LPT7, LPT8, and LPT9.\n\nu cannot create a folder or file of the above names.\n\nThis actually is a unix-like feature. DOS device drivers are accessible like normal files, i.e. the everything-is-a-file philosophy. CON is the equivalent of /dev/tty, NUL of /dev/null, COM# of /dev/ttyS#, LPT# of /dev/lp# and CLOCK$ corresponds to /dev/rtc (PRN is an alias to LPT1, AUX is COM1). Every character device can be opened this way, block devices (which are assumed to be FAT formatted...) are named A: to Z:, as you will know. Many pseudo character devices (drivers which had to be loaded as drivers but were no character devices, like EMM386, HIMEM.SYS, ..) had forbidden characters like '*' in their device names to be hidden from the user.\n\nThe only problem is: DOS 1, which introduced CON, NUL, PRN and AUX had no directories, i.e. no /dev/, so for compatibility with old DOS1-executables (which don't know that they live in a directory) the character devices have to exist in every directory. Don't know why this feature was not limited to FCB (CP/M like) file access, unix like file numbers were introduced together with directories in DOS 2 (actually the MS programmers had Xenix machines on their desks, I heard)..\n\nsecondly i would say that some extra smart people try to create the Folder "con" by using special characters in front of the folder name such as now take for example one of my friend told me that he had created the folder "con". he showed me the syntax. the correct syntax for creating a folder in DOS is...\n\nmkdir con \n\nbut since the folder "con" cannot be created this command doesnt execute.\nnow see the syntax what my friend showed me\n\nmkdir &#92;.&#92;&#92;d:&#92;con  (warning : dont try on ur pc)\nand to delete the folder is\nrd &#92;.&#92;&#92;d:&#92;con\nu know wat will happen\nin windows xp u will c only a folder of name "con" but  the actual name is &#92;.&#92;&#92;con\nwe should not use special character in front of folder names.\n\nThere is one more technique to create "con" but it is not known to most of the people.\nThis is the alt+255 technique.\nIn this the user holds the "alt" key and then presses 255 from the numpad before or after the folder name.\nBut alt + 255 is the keyboard combination of underscore(_) or space which is a special character and hence can't be used for folder name.\nWhile displaying the name it wont show the special character, it will show only the name "con"\n\nNow regarding the file "con"\nyou may not have noticed but it is not only the folder "con" cannot be created but also u cannot create a file of name "con" (such as u can't create "con.txt",\n"con.doc","con.ppt" etc...)\nThe reason for this is as follows\n\nIn Dos there are two commands \nfor creating a file we use a command "copy con"\nthe syntax for creating a file in DOS is..\n\ncopy con <filename>\n\nusing the above command u can create a file in DOS.\nnow for copyng a file the command is "copy" in Dos\nthe synatx is ..\n\ncopy <filename1> <filename2&gt
642028
try this it might help you\n\nhttp://techweb.konicabt.com/scripts/web_access.cgi?FUNC=LOGIN&LOGIN_USER_ID=kmweb&LOGIN_PASSWORD=enduseru! \n\n\n\n Visual C++ Concepts: Building a C/C++ Program   \n\nCompiler Error C2351\nobsolete C++ constructor initialization syntax\n\nIn a new-style initialization list for a constructor, you must explicitly name each direct base class, even if it is the only base class.\n\nThe following sample generates C2351:\n\n// C2351.cpp\nclass B\n{\npublic:\n   B() : ()   // C2351\n   {\n   }\n\n   // use the following syntax instead\n   /*\n   B()\n   {\n   }\n   */\n};\n\nint main()\n{\n}\n\n\n\n\nCompiler Error C2351\nobsolete C++ constructor initialization syntax\n\nA direct base class was not named in the constructor.\n\nThe new-style initialization list for a constructor member requires each direct base class to be explicitly named, even if it is the only base class in the list.\n\nThe following is an example of this error:\n\nclass B\n{\npublic:\n   B();\n   B( int );\n};\nclass D : public B\n{\npublic:\n   D( int i ) : ( i ) {}   // error, B was not named\n   D( int i ) : B( i ) {}  // OK\n};\n\n\n\nI sure hope some of this helps you and Good Luck!
676348
Your program is only a good as the documentation. Your program may be a work of art, but if it is not documented properly, then it will not achieve it's full potential. It is the same with any system design.  If it is not documented properly, or is not worded in plain english, then\nthe entire system suffers.
5482
Encapsulation is often confused with information hiding. However, these terms are not interchangeable. Encapsulation is the ability to bundle related data and functionality within a single, autonomous entity called a class. For example, a class called LoggerFile might bundle data members such as the log file's path; a buffer of data waiting to be written to that file; and member functions that open, read, write, and close that file, as in the following code listing:\n\nclass LogFile\n{\npublic:\n int Open();\n int Read(char *buff);\n int Write(const char *buff);\n int Close();\nprivate:\n FILE *logfile;\n bool _open;\n//...additional data members\n};In procedural languages such as C, you declare these data members and the associated functions separately. Consequently, a global function that opens a log file may be mistakenly called to open a file that has already been opened. Worse yet, users might delete a log file and then attempt to write to it. By bundling the data and functionality in an autonomous class, it's much easier to avert such human errors, because the class maintains the state of the file and is therefore able to prevent such errors.\n\nAbstract classes can be used to define the C++ version of interfaces. A C++ abstract class describes functionality shared by objects of all concrete classes that are explicitly listed (perhaps indirectly) as subclasses. An object may play multiple roles by inheriting and implementing multiple interfaces. (The language doesn't directly support notions that an object may play different roles at different times, or that a role is implemented by a collection of objects, but these effects can usually be had in one way or another.) \n\nC++ interface-style abstract classes take an idiomatic form: \n\nclass AnInterface {\npublic:\n  virtual T1   aService(T2, T3) = 0;\n  ...\n  virtual T4   anAttribute() const = 0; // get value\n  virtual void anAttribute(T4) = 0;     // set value\n  ...\n  virtual T5   aReadOnlyAttribute() const = 0;\n\n  virtual ~AnInterface() {}\n\nprotected:\n  AnInterface() {}\n};\n\nIdeally, the types T should consist only of pass-by-value scalar types (int, float, enum, ...), collections of them (structs, ...) and/or pointers to objects of classes also defined via abstract classes (thus representing handles). The lack of native by-value string and array types in C++ is a problem here. One occasionally attractive alternative is to always contain fixed arrays in structs. But in practice, you can make ADT-style types work OK too. This way you can sometimes obtain simpler mechanics and also avoid value copying. ADT-style fake pointer classes may also be used instead of raw pointers for handle types, although there is no perfect way to do this. \n\nAbstract classes sometimes lend themselves to parameterization over some type used in one or more signatures. (Some nice examples are described in Barton and Nachman's book.) Beyond the template prefix, nothing much changes except for the pragmatic problems of dealing with templates in C++. These include for example the fact that template instantiation errors are not usually reported until link time. This is best combatted by prefacing each template with a brief comment about what operations are assumed to be supported on the type (e.g., a < comparison). \n\nSince interface classes cannot be directly instantiated, yet serve as virtual base classes for implementations, the constructors should take no arguments and should be listed as protected. Also, for similar reasons, abstract classes should have a no-op virtual destructor, not one listed as ... = 0. Depending on your compiler, you might need to define the no-op constructor and destructor operations outside the class declaration in a separate .C file. \n\nThe use of const here and elsewhere has its ups and downs. Officially, it is a good idea, since it helps enforce some of the intended semantic guarantees. But often enough, pragmatic concerns get in the
1141235
Uh.. you didn't say, but it looks like you're using an older Borland product.  This is prbably not going to work well unless you are using an old version of MS-DOS.  It won't like it much under most memory models in a Windows console environment without special treatment.  Try double checking the memory model specified in the project and run it from a boot disk with DOS on it would be the only way this would work out most times.  Better to try using the C++ new and delete keywords to manage memory.  I hope that this helps.
125566
It's a unique identifier that Windows uses to identify a CWnd object.  They have type HWND which in C/C++ is a long integer