Tuesday, September 9, 2008

Apple Certification Exam 9L0-509

The assignment operator, =, must be a member function, and is given default behavior for user-defined 9L0-509 classes by the compiler, performing an assignment of every member using its assignment operator. This behavior is generally acceptable for simple classes which only contain variables. However, where a class contains references or pointers to outside resources, 9L0-402 Exam the assignment operator should be overloaded (as general rule, whenever a destructor and copy constructor are needed so is the assignment operator), otherwise, for example, two strings would share the same buffer and changing one would change the other.

In this case, an assignment operator should perform two duties:

1. clean up the old contents of the object
2. copy 9L0-509 Braindump the resources of the other object

For classes which contain raw pointers, before doing the assignment, the assignment operator should check for self-assignment, which generally will not work (as when the old contents of the object are erased, they cannot be copied to refill the object). Self assignment is generally a sign of a coding error, and thus for classes without raw pointers, 9L0-402 this check is often omitted, as while the action is wasteful of cpu cycles, it has no other effect on the code.

Microsoft-TS Certification Exam 70-648

All of the bitwise 70-621 operators are binary, excepting complement, which is unary. It should be noted that these operators have a lower precedence than the arithmetic operators, so if ^ were to be overloaded for exponentiation, x ^ y + z may not work as intended. Of special mention are the shift operators, << and >>. These have been overloaded in the standard library for interaction 70-642 with streams. When overloading these operators to work with streams the rules below should be followed:

1. overload << and >> as friends (so that it can access the private variables with the stream be passed in by references
2. (input/output modifies the stream, and copying is not allowed)
3. the operator 70-648 should return a reference to the stream it receives (to allow chaining, cout << 3 << 4 << 5)

Tuesday, September 2, 2008

Apple Certifications Exam 9L0-509

If you are one of the many people who used to use and have since switched to a different editor, you may already be 9L0-402 familiar with the problem of retrieving your own information from certain types of files. Or perhaps you switched from one operating system to another, from Amiga to Windows, or Windows to Macintosh. Stated simply, file formats for different software far too often leave your information scrambled in a way you cannot decipher again years later.

If this seems a bit theoretical to you then here are some stories to illustrate the issue of choosing the right format for your information.

The English Tourist

A tourist walks into a 9L0-509 very nice restaurant in a lovely village in the French countryside and mutters in English "Are you still serving lunch?" No one reacts, so he says louder, "Do you have a TABLE where I might DINE?" Recognizing a few words and realizing that the tourist must only speak English or isn't interested in trying his French, one of the employees goes off to find someone who might be able to help this ignorant tourist.

Cisco CCNP Certification 642-892

Planning for an unpredictable future is known as future proofing, although you can't really know if you are 642-642 future proof you can practice risk reduction and learn from the mistakes of history. This article focuses on future proofing of . This article gives tips for creating files in a manner which makes them easy to preserve and later access, and for avoiding pitfalls that could make your files difficult to access later. Looking after the files you already have is known as .

Where future proofing and digital preservation deal with the rather etheric matter of electronic files and 642-825 their , then your next concern is the media on which your information is stored. That is an area of study in itself, and is not the subject of this article.

Both future proofing of information and the media it is stored on are vital in any thorough review of your IT systems. Will you be able to read the files you're working on now in 5 years time? Do you know if all the old files you have now are still readable?

The chance of electronic 642-892 files being readable in 5 or 10 years is not something to leave up to chance. Active intervention is needed in most cases. Migrating to software/hardware that supports openly published standards is the most effective single step in any plan to future-proof.