|
Ennis Ray Lynch, Jr. wrote: if saving typing concern is the primary concern of a Software Developer
I always wondered just what that primary concern had to be
But on a serious note, I suspect that Pascal language fame was so short and C spread so fast mainly because BEGIN/END was replaced with {}
|
|
|
|
|
If you want to save on typing use resharper.
VB style keywords belong in VB. Why bastatrdize C# , it make no sense. If you are a C# developer that wants to use the with keyword to save some typing then then switch to VB. Just remember that the time that you save by using the with keyword will be lost by having to type those ridiculous if... then... end if statements.
modified on Wednesday, October 8, 2008 5:16 AM
|
|
|
|
|
sucram wrote: Just remember that the time that you save by using the with keyword will be lost by having to type those ridiculous if... then... end if statements.
So by adding WITH to C# you get the time-saving and avoid the IF THEN END statements...
(By the way, I voted NO too. I just don't think your reasoning is fully thought through.)
|
|
|
|
|
Your right I went into a blinding range when I saw the survey and my primeval instincts took over. Hence my grammar and logical sentence construction ability was reduced to grunts.
modified on Wednesday, October 8, 2008 11:05 AM
|
|
|
|
|
I voted you a 5, just because I was in the mood. Yeah, that's right, feel thy wrath! Muwahahahaha!
|
|
|
|
|
Sorry, I couldn't resist.
/ravi
|
|
|
|
|
yeah and while we're on the topic, what's that got to do with musical notes?
|
|
|
|
|
Though it (VB) can not stand to compete against other languages, for a significant percentage of software professionals it is an essential breadwinner.
Vasudevan Deepak Kumar
Personal Homepage Tech Gossips
All the world's a stage,
And all the men and women merely players.
They have their exits and their entrances;
And one man in his time plays many parts... --William Shakespeare
|
|
|
|
|
I was only kidding. I don't have religious opinions on programming languages, code editors or religion.
/ravi
|
|
|
|
|
Ravi Bhavnani wrote: What's VB?
VB = C# - curly braces - semicolons + Dim
|
|
|
|
|
+ My namespace.
/ravi
|
|
|
|
|
Nemanja Trifunovic wrote: VB = C# - curly braces - semicolons + Dim
+ Me keyword and everything totally messed up due to a backward compability with a extremely inefficient and over-keyworded language.
Greetings - Gajatko
Portable.NET is part of DotGNU, a project to build a complete Free Software replacement for .NET - a system that truly belongs to the developers.
|
|
|
|
|
gajatko wrote: over-keyworded language
Proof? Examples?
|
|
|
|
|
I mean: a lot of redutant and hilarious keywords, which can be replaced by intuitive symbols. Do you really need a proof for this obvious thing? Here are examples:
Then, End If, End While, End X, Dim, As, Implements, Handles, Until, & operator, ReadOnly, OverLoads, CDate, CChar, CStr, CSng etc. (and 11 more), ReDim, Preserve, WriteOnly , etc. etc.. There are much more redutancies in this ankward sandbox programming language, but I think that's enough for now. Cheers.
Greetings - Gajatko
Portable.NET is part of DotGNU, a project to build a complete Free Software replacement for .NET - a system that truly belongs to the developers.
|
|
|
|
|
Yeah I see what you mean. I'm still thinking in a classic VB way since I don't use .NET much. But, I see how some of those (not all, some are just verbose) could overlap the BCL functionality.
|
|
|
|
|
Nemanja Trifunovic wrote: VB = C# - curly braces - semicolons + Dim
I'm still happy to be a dinosaur too. Rawr!!
|
|
|
|
|
VB also supports an 'Optional' keyword. C#, for some reason supports only overloading and does not support the optional keyword.
Vasudevan Deepak Kumar
Personal Homepage Tech Gossips
All the world's a stage,
And all the men and women merely players.
They have their exits and their entrances;
And one man in his time plays many parts... --William Shakespeare
|
|
|
|
|
Yeah, that's a tough one to swallow coming from C++ as well. Although with a bit of prep work, you can kinda fake it by passing in an object and using initializers. IMHO, C# should build this into the compiler and just give us named parameters with default values...
---- You're right.
These facts that you've laid out totally contradict the wild ramblings that I pulled off the back of cornflakes packets .
|
|
|
|
|
That's pushing the envelope a bit far! "Optional" is really only useful in VB to simulate polymorphism, which C# already supports.
Public Sub MyExample(intLength As Integer, Optional intWidth As Integer)
' Some code
End Sub
-- C#
public void MyExample(Length as int)
{
}
public void MyExample(Length as int, Width as int)
{
}
http://mytechworld.officeacuity.com
|
|
|
|
|
I disagree:
public void MyExample( int length, optional int height = 0, optional int width = 0 )
{
}
is better (and clearer) than
public void MyExample( int length )
{
MyExample( length, 0 );
}
public void MyExample( int length, int height)
{
MyExample( length, height, 0 );
}
public void MyExample( int length, int width )
{
MyExample( length, 0, width );
}
public void MyExample( int length, int height, int width )
{
}
|
|
|
|
|
Why bother with a keyword? The compiler should be able to handle
public void MyExample( int length, int height = 0, int width = 0 ){
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
You are right. 'Optional' is just syntatic sugar that would make it more visible.
|
|
|
|
|
No - VB.NET has polymorhism too
Optional is mainly used for dealing with OLE Automation (particularily of Office apps) which have optional parameters....
But doesn't C# have a var keyword for that?
|
|
|
|
|
That's not polymorphism, that's overloading, and is entirely separate issue from default (optional) parameters - for example C++ supports both.
|
|
|
|
|
And here's why:
pane.YAxis.IsVisible = true;
pane.YAxis.Type = AxisType.Linear;
pane.YAxis.Scale.FontSpec.Size = 9;
pane.YAxis.Scale.FontSpec.IsAntiAlias = true;
pane.XAxis.IsVisible = true;
pane.XAxis.Type = AxisType.Date;
pane.XAxis.MajorTic.IsInside = false;
pane.XAxis.MajorTic.IsOpposite = false;
pane.XAxis.MinorTic.IsInside = true;
pane.XAxis.MinorTic.IsOpposite = true; Becomes:
with (pane.YAxis)
{
.IsVisible = true;
.Type = AxisType.Linear;
with (.Scale.FontSpec) { .Size = 9; .IsAntiAlias = true; }
}
with (pane.XAxis)
{
.IsVisible = true;
.Type = AxisType.Date;
with (.MajorTic) { .IsInside = false; .IsOpposite = false; }
with (.MinorTic) { .IsInside = true; .IsOpposite = true; }
}
---- You're right.
These facts that you've laid out totally contradict the wild ramblings that I pulled off the back of cornflakes packets .
|
|
|
|