> > This subject is not belong to me directly, but I am also concern about the length of coding in .Net compared to VFP, I have this to say.
> >
> > - Less coding number of line does not mean faster execution.
> > - Both of you and Camil mention 20 lines of code, where I can ONLY see 2 lines in your code (if you remove the variable declaration and comments and the line separator)
> >
> > btw: Nice code.
> >
> > Samir Ibrahim
>
> Thanks Samir,
> -Yes I completely agree number of line codes does not mean a faster execution or better productivity (and a .Net coder would say I could write that in a single line:)
> -I know it is not 20 lines, just wanted to signify it wouldn't matter if it were 2 or 20:)
>
> Cetin Basoz
>
>
.Net has got better.Think about moving - check my blog:
>
Blog (main)>
Blog (mirror)I know what mean by saying "just wanted to signify it wouldn't matter if it were 2 or 20:)"
But this whole discussion was about making 1 line VFP code work in C# with 20 lines of code, which is not correct.
my point is: is that discussion was gonna exist if comparing 1 line with 2 line?
Your example is 2 lines length, which is more than acceptable, unless a comparison will be made to compare char/line also :)
I had to admit that this was my concern also (coding length) so when I see a vfp function converted to .net (vb or c#) in just 2 lines, then is good code and unique one.
Samir Ibrahim