Welcome to the Lounge

Sinisa Hajnal wrote:

case sensivity is worst

Sinisa Hajnal wrote:

I always have option strict on

Sinisa Hajnal wrote:

Compiling same ILM matters

namespace EnumTestCS
{
  public static class EnumTestCS
  {
    public static void Main()
    {
      System.Console.WriteLine ( System.Text.RegularExpressions.RegexOptions.None ) ;
    }
  }
}

namespace EnumTestVB
  module EnumTestVB
    sub main
      System.Console.WriteLine ( System.Text.RegularExpressions.RegexOptions.None )
    end sub
  end module
end namespace

Sinisa Hajnal wrote:

something that YOU don't know how to do in VB.NET.

namespace EventTest
{
  public class EventTest
  {
    public delegate int F() ;
    public event F E ;
    private void RaiseE() { E() ; }
  }
}

PIEBALDconsult wrote:

Case insensitivity made sense when we used punch cards, teletypes, or early terminals that didn't support lowercase anyway. Now it only leads to confusion and increased compile times.

PIEBALDconsult wrote:

Does that disable the ability to leave off the parentheses on method calls?

PIEBALDconsult wrote:

Consider these two simple programs that execute the exact same statement. Do they produce the same IL? Do they behave the same?

Namespace EnumTestCS
	Public NotInheritable Class EnumTestCS
		Public Shared Sub Main()
			System.Console.WriteLine(System.Text.RegularExpressions.RegexOptions.None)
		End Sub
	End Class
End Namespace

PIEBALDconsult wrote:

While I may be the only person in the world who needs to do this, show me how it can be done in VB.net .

Namespace EventTest
	Public Class EventTest
		Public Delegate Function F() As Integer
		Public Event E As F
		Private Sub RaiseE()
			RaiseEvent E()
		End Sub
	End Class
End Namespace

Sinisa Hajnal wrote:

Except when it is autocorrected

Sinisa Hajnal wrote:

you compared class and module

Sinisa Hajnal wrote:

Public Delegate Function F() As Integer

MikeTheFid wrote:

listening to an orgasm festival

MikeTheFid wrote:

a fire alarm manufacturer

MikeTheFid wrote:

the performance of the system as a whole sucked

public class SanderRossel : Lazy<Person>
{
   public void DoWork()
   {
      throw new NotSupportedException();
   }
}

Quote:

So the alarm wouldn't go off until the whole place was burned to the ground?

Sander Rossel wrote:

Should I be made responsible for a project with a tight deadline I'd go with... C# and SQL Server, because, well, that's what I know

patbob wrote:

the ability for others to be able to maintain it is an overriding (unstated) requirement

public class SanderRossel : Lazy<Person>
{
   public void DoWork()
   {
      throw new NotSupportedException();
   }
}

Kirk 10389821 wrote:

I think knowing your ONE tool very well makes more sense than being a generalist.

Kirk 10389821 wrote:

Currently I am working with Cobol, RPG, CL, PHP, Oracle PL/SQL, SQL, ASP, and Delphi

Kirk 10389821 wrote:

that FIRST job of a developer should be to correctly identify the problem being solved, and then identify the right solution for the job

Kirk 10389821 wrote:

coded myself out of a job

public class SanderRossel : Lazy<Person>
{
   public void DoWork()
   {
      throw new NotSupportedException();
   }
}