Actually there is no
article yet. I'm at the outline stage and would
like some feedback from the K5 audience on what
they think. The first paragraph is my current lead
in and the format of the article is that it will be
a table of contents with links pointing back to a
full article on my homepage. Ok, so here's what the
rest of the article would look like...
Table of Contents- The More Things
Change The More They Stay The Same:
This section describes concepts and language
features that are almost exactly the same in C#
and Java.- We Are All
Objects
- Keyword
Jumble
- Of Virtual Machines
and Language Runtimes
- Heap Based Classes
and Garbage Collection
- Arrays Can Be
Jagged
- No global
methods.
- Interfaces, Yes.
Multiple Inheritance, No.
- The Same But Different
This section describes concepts and language
features that differ either only in syntax or
in some similarly minor manner between C# and
Java.
- Inheritance Syntax
- Run Time Type Identification (is
operator)
- Namespaces
- Destructors and Finalizers
- Synchronizating Code Blocks
- Inner classes
- Access Modifiers
- Reflection
- Declaring Constants
- Primitive Types
- An Ever So Slight Feeling of Dejà
Vu
This section describes concepts and language
features that exist in C# that are similar to
those that exist in Java but with a significant
difference.
- Operator Overloading
- switch statment
- Exceptions
- Cross Language Interoperability
- Assemblies
- Collections
- goto (no longer considered harmful)
- Virtual Methods
- File I/O
- Object Serialization
- Documentation Generation from Source Code
Comments
- Multiple Classes in a Single File
- Importing Libraries
- Now For Something Completely
Different
This section describes language features and
concepts that exist in C# and have no Java
counterpart.
- Enums
- Value Types (Structs)
- Run Time Type Identification (as
operator)
- Delegates
- Events
- Attributes
- Indexers
- foreach Statement
- Properties
- Pointers
- PreProcessor
- Aliases
- Boxing
- Pass by Reference
- params Keyword
- Verbatim Strings
- Static Constructors
- Overflow Detection
- Explicit Interface Implementation
So what do you guys think?