[Message Deleted]
-
meenakumar wrote:
Which one you prefer, like or feel more challenging..
I probably prefer web development, due to the (slightly) better documentation offered, but I have occasions with both where I want to throw myself out of a third storey window..
meenakumar wrote:
does c++ has scope still?
I still code with it, although I guess some would argue that you can get more from something like C# more easily as its a higher-level language, but I'm not particularly a fan of .NET anyway. Regards, --Perspx
Don't trust a computer you can't throw out a window
-- Steve Wozniak
Perspx wrote:
documentation
Cough, splutter, cough, spit, CSS? Better documentationz? Nooit!
-
I can only speak for myself, but desktop seems far less stressful and more flexible than web. The last web project we did (a K2.NET workflow solution) was a pain on so many levels - none of which would have been an issue on the desktop. Then again, my idea of fun is writing plug-in code for Visual Studio in C++/WTL, so what would I know...? :rolleyes:
Anna :rose: Having a bad bug day? Tech Blog | Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
modified on Friday, September 19, 2008 4:48 PM
Anna-Jayne Metcalfe wrote:
so what would I know...? Roll eyes
:~
-
leonej_dt wrote:
The same thing goes for C#.
Nooit! :rolleyes:
Brady Kelly wrote:
leonej_dt wrote: The same thing goes for C#. Nooit!
C# doesn't allow me to mess with pointers, define templates or even allocate objects in the stack. As far as I know, in C#, you can only use references in method parameters, that means you can't return a reference to a value type. When I need to do OOP, C# doesn't allow me to do multiple inheritance. And when I don't need to do OOP, C# forces me to write static classes. In other words, C# tries to tell me what to do, what to expect and how to think.
If you can play The Dance of Eternity (Dream Theater), then we shall make a band.
-
Brady Kelly wrote:
leonej_dt wrote: The same thing goes for C#. Nooit!
C# doesn't allow me to mess with pointers, define templates or even allocate objects in the stack. As far as I know, in C#, you can only use references in method parameters, that means you can't return a reference to a value type. When I need to do OOP, C# doesn't allow me to do multiple inheritance. And when I don't need to do OOP, C# forces me to write static classes. In other words, C# tries to tell me what to do, what to expect and how to think.
If you can play The Dance of Eternity (Dream Theater), then we shall make a band.
leonej_dt wrote:
C# doesn't allow me to mess with pointers
Ever heard of
unsafe
code?GCHandle
?leonej_dt wrote:
define templates
C# has generics - not quite as powerful as templates, but the idea is the same (parameterized types).
leonej_dt wrote:
even allocate objects in the stack
struct
?leonej_dt wrote:
As far as I know, in C#, you can only use references in method parameters, that means you can't return a reference to a value type.
Nope, you can pass
struct
s both into and out of a method. You can optionally pass them by reference using theref
keyword.leonej_dt wrote:
C# doesn't allow me to do multiple inheritance. And when I don't need to do OOP, C# forces me to write static classes.
No contesting these points :)
Regards Senthil [MVP - Visual C#] _____________________________ My Home Page |My Blog | My Articles | My Flickr | WinMacro
-
leonej_dt wrote:
C# doesn't allow me to mess with pointers
Ever heard of
unsafe
code?GCHandle
?leonej_dt wrote:
define templates
C# has generics - not quite as powerful as templates, but the idea is the same (parameterized types).
leonej_dt wrote:
even allocate objects in the stack
struct
?leonej_dt wrote:
As far as I know, in C#, you can only use references in method parameters, that means you can't return a reference to a value type.
Nope, you can pass
struct
s both into and out of a method. You can optionally pass them by reference using theref
keyword.leonej_dt wrote:
C# doesn't allow me to do multiple inheritance. And when I don't need to do OOP, C# forces me to write static classes.
No contesting these points :)
Regards Senthil [MVP - Visual C#] _____________________________ My Home Page |My Blog | My Articles | My Flickr | WinMacro
S. Senthil Kumar wrote:
Ever heard of unsafe code? GCHandle?
Of course I know what unsafe code is. But if I want 98% of my code to be unsafe, I'd rather use C++.
S. Senthil Kumar wrote:
C# has generics
Generics don't do what I want them to do. Besides, there is not such a thing as generic specialization.
S. Senthil Kumar wrote:
leonej_dt wrote: even allocate objects in the stack struct?
Structs don't allow inheritance.
S. Senthil Kumar wrote:
you can pass structs both into and out of a method. You can optionally pass them by reference using the ref keyword.
But that syntax sucks.
S. Senthil Kumar wrote:
leonej_dt wrote: C# doesn't allow me to do multiple inheritance. And when I don't need to do OOP, C# forces me to write static classes. No contesting these points
There are the main reasons why I use C++.
If you can play The Dance of Eternity (Dream Theater), then we shall make a band.
-
S. Senthil Kumar wrote:
Ever heard of unsafe code? GCHandle?
Of course I know what unsafe code is. But if I want 98% of my code to be unsafe, I'd rather use C++.
S. Senthil Kumar wrote:
C# has generics
Generics don't do what I want them to do. Besides, there is not such a thing as generic specialization.
S. Senthil Kumar wrote:
leonej_dt wrote: even allocate objects in the stack struct?
Structs don't allow inheritance.
S. Senthil Kumar wrote:
you can pass structs both into and out of a method. You can optionally pass them by reference using the ref keyword.
But that syntax sucks.
S. Senthil Kumar wrote:
leonej_dt wrote: C# doesn't allow me to do multiple inheritance. And when I don't need to do OOP, C# forces me to write static classes. No contesting these points
There are the main reasons why I use C++.
If you can play The Dance of Eternity (Dream Theater), then we shall make a band.
leonej_dt wrote:
But if I want 98% of my code to be unsafe, I'd rather use C++.
If 98% of my code is unsafe, I wouldn't look at the .NET framework at all, never mind C#. And it's kind of pointless to argue that a language designed to run on top of such a framework doesn't support unsafe features.
leonej_dt wrote:
Generics don't do what I want them to do. Besides, there is not such a thing as generic specialization.
I don't know how you use templates - if you're a really aggressive user (think Alexi Alexadrescue's book), you'll probably find generics don't fit the bill. But for type safe containers and such, generics work great.
leonej_dt wrote:
Structs don't allow inheritance.
Yes, but how is it related to allocating them on the stack? Contrast this to Java, which simply doesn't allow user defined types to exist on the stack.
leonej_dt wrote:
But that syntax sucks.
Syntax is a subjective matter, but I'm surprised to hear this from a C++ programmer. How different is typing ref from typing an & or a *?
Regards Senthil [MVP - Visual C#] _____________________________ My Home Page |My Blog | My Articles | My Flickr | WinMacro
-
leonej_dt wrote:
But if I want 98% of my code to be unsafe, I'd rather use C++.
If 98% of my code is unsafe, I wouldn't look at the .NET framework at all, never mind C#. And it's kind of pointless to argue that a language designed to run on top of such a framework doesn't support unsafe features.
leonej_dt wrote:
Generics don't do what I want them to do. Besides, there is not such a thing as generic specialization.
I don't know how you use templates - if you're a really aggressive user (think Alexi Alexadrescue's book), you'll probably find generics don't fit the bill. But for type safe containers and such, generics work great.
leonej_dt wrote:
Structs don't allow inheritance.
Yes, but how is it related to allocating them on the stack? Contrast this to Java, which simply doesn't allow user defined types to exist on the stack.
leonej_dt wrote:
But that syntax sucks.
Syntax is a subjective matter, but I'm surprised to hear this from a C++ programmer. How different is typing ref from typing an & or a *?
Regards Senthil [MVP - Visual C#] _____________________________ My Home Page |My Blog | My Articles | My Flickr | WinMacro
S. Senthil Kumar wrote:
Yes, but how is it related to allocating them on the stack?
In one of my projects, an MFC dialog-based application, I have a class called CGraficosDC derived from CClientDC. In the main dialog's class, there are buttons whose event handlers look like this:
void CGraficosDlg::OnEjercicio1() { CGraficosDC dc(this); // this object lives in the stack // ... }
S. Senthil Kumar wrote:
Contrast this to Java, which simply doesn't allow user defined types to exist on the stack.
Java sucks, period. But that is off-topic. [Edit: The following text was added]
S. Senthil Kumar wrote:
leonej_dt wrote: But if I want 98% of my code to be unsafe, I'd rather use C++. If 98% of my code is unsafe, I wouldn't look at the .NET framework at all, never mind C#.
Did you think I meant C++/CLI? C'mon! [Second edit: The following text was added]
S. Senthil Kumar wrote:
Syntax is a subjective matter, but I'm surprised to hear this from a C++ programmer. How different is typing ref from typing an & or a *?
What sucks is the fact I can't write a routine like this in C#:
ReturnType& CUndocumented::AMethod(ParamType1 par1, ParamType2 par2) { // do something }
If you can play The Dance of Eternity (Dream Theater), then we shall make a band.
-
Harvey Saayman wrote:
Your going to start a language war
Whose language you looking at? You mean to say you**'**re going to start a language war.
My language is bigger than yours ;P
Harvey Saayman - South Africa Junior Developer .Net, C#, SQL
you.suck = (you.Passion != Programming & you.Occupation == jobTitles.Programmer)
1000100 1101111 1100101 1110011 100000 1110100 1101000 1101001 1110011 100000 1101101 1100101 1100001 1101110 100000 1101001 1101101 100000 1100001 100000 1100111 1100101 1100101 1101011 111111 -
My language is bigger than yours ;P
Harvey Saayman - South Africa Junior Developer .Net, C#, SQL
you.suck = (you.Passion != Programming & you.Occupation == jobTitles.Programmer)
1000100 1101111 1100101 1110011 100000 1110100 1101000 1101001 1110011 100000 1101101 1100101 1100001 1101110 100000 1101001 1101101 100000 1100001 100000 1100111 1100101 1100101 1101011 111111Harvey Saayman wrote:
yours
That's better. :laugh:
-
Perspx wrote:
documentation
Cough, splutter, cough, spit, CSS? Better documentationz? Nooit!
Yes, but at least W3C acts as a standards body; Microsoft is the standards body for Windows development, and after traversing to the depths of MSDN, I never want to go there again :sigh: Regards, --Perspx
Don't trust a computer you can't throw out a window
-- Steve Wozniak
-
Anna-Jayne Metcalfe wrote:
so what would I know...? Roll eyes
:~
Now I'm confused. More coffee please!! :-\
Anna :rose: Having a bad bug day? Tech Blog | Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
OK. But you have to buy them yourself and bill them against the total balance of the contract. We are not responsible for cost overruns on your end.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
I work only on hourly basis currently. ;P I don't do fixed price work, so I guess we don't match.
-
meenakumar wrote:
windows or web development?? why? does c++ has scope still? or should I turn to dot net?
Forget programming. Write haiku. Regards.
In January you said "money in April" B. Python
Uros Calakovic - Urke wrote:
Forget programming. Write haiku. Regards.
int main() // my haiku { printf("I write Haiku also\n"); printf("program C.\n");}
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
-
Yes, but at least W3C acts as a standards body; Microsoft is the standards body for Windows development, and after traversing to the depths of MSDN, I never want to go there again :sigh: Regards, --Perspx
Don't trust a computer you can't throw out a window
-- Steve Wozniak
Perspx wrote:
Microsoft is the standards body for Windows development
Not quite. C# is an open (ECMA) standard, with a free compiler and spec.