C#

foreach (var line in allLines.Where(s => s.Any(c => !(char.IsWhiteSpace(c) || char.IsDigit(c)))))
//I think using 2 operator instead of 3 will execute faster if the compiler doesn't optimize that
{ }

allLines.Where(s => s.Any(c => !(char.IsWhiteSpace(c) || char.IsDigit(c)))).Select(s => s.Length);

Marc Clifton wrote:

So. That's, umm, disappointing. I certainly don't want to process a million character string if the first char in the string is 'A'.

leppie wrote:

I do however believe that SQL will be optimized if running the same query over a database source.

led mike wrote:

Huh? I'm LINQless so I have no idea what that means.

leppie wrote:

That probably does not make any sense

char[] chars = failure.ToCharArray();
bool bad = false;
for (int n = 0; !bad && n < chars.Length; n++)
    if (!Char.IsDigit(chars[n]) && !Char.IsWhiteSpace(chars[n]))
        bad = true;

led mike wrote:

So then where does some sort of performance gain come into effect in the current example? I mean how are the expression trees etc., going to faster than code like:

leppie wrote:

But it's easier to write

leppie wrote:

But you can do something with same effect.

string failure = "123 512512512 1";
bool bad = (from p in failure.ToCharArray()
           where !char.IsDigit(p) && !char.IsWhiteSpace(p)
           select p).Count() > 0;
Console.WriteLine("{0}\n", bad);

captjack wrote:

I read somewhere that the buffers might need to get flushed/reset, but can't seem to find that method.

using (FileStream fs = new FileStream("c:\\textFile.txt", FileMode.Open, FileAccess.ReadWrite)) {
   using(StreamWriter sw = new StreamWriter(fs)) {
      sw.BaseStream.Seek(10, SeekOrigin.Begin);
      sw.Write("0005");
      sw.Flush();
      sw.BaseStream.Seek(1, SeekOrigin.Begin);
      sw.Write("Test");
   }
}

cmdinsert.CommandText = "insert into Users(Firstname,LastName,Username,Password,Email)   Values(?,?,?,?,?)";