Hi Cetin:

Looks like a nice idea to implement. I believe we could put a two phased approach:

1. Exposing the function in the Wiki to have the people comment in the implementation and improve it. The developers could comment and also write his / her own implementation leaving the original posting intact, this way we could avoid to introduce a non sense change.

2. Qualified submitter who take the function and write it to the Source Code repository, after the function passes the tests.

And yes you could write the function in another .NET language but this is not needed at all. Our proposed extensions allows you to write code using strong typing, stack based variables, .NET delegates, .NET Events, and almost everything you could in another languages in the VFP Language, with the advantage you get very fast code.

We thank you for supporting us, and sincerely I believe the Compiler for .NET is truly the way to go the .NET route. I don't want to lose the high level capabilities of VFP, it would be like a big step backward to lose the 4GL (Fourth Generation Language) Capabilities and return to a 3GL like C# or VB. By the way if you read the LINQ syntax you could appreciate C#, VB are morphing into something like a 3.1GL so why you would like to wait years to have those language resemble VFP when we have it now. I'm even wondering if the proposed LINQ syntax extensions are the way to go, they don't look so clean like the VFP syntax, but I'm skewed after all I'm a VFP programmer and have the Fox in the hearth.

By the way, we would like to hear your feedback about the proposed extensions. Someone with your knowledge could help us to shape this into the best for us the VFP programmers.

We honestly expect to build a valuable product, one that you would have to try very hard to find a reason not to use. So I hope to see you in a year using the compiler for both, taking your old code to .NET and for your new programming.

Samuel

>Pertti,
>(Please do not take my comments as a negative act. I don't have such an intention and actually already talked with my biz manager to buy the product for supporting whether or not we use it).
>
>I am somewhat worried about open-source style write/test and send. Instead each function implementaion could be placed somewhere (like wiki or anyhting similar) to be edited and perfected by academic level discussions (here I do not really mean to discuss it at academies, but as sometimes we all do, discuss on the code to find the best implementation - we do it here too much to find a better performing code sample for example). Honestly at this moment Fabio comes to mind as a perfect QA manager:)
>For example I'd at least add m. in your code:) We all have timing problems but we all would give a hand to such a thing I think.
>(and I wonder if we could also write implementation from .Net direction too, ending an enhanced version of functions etc. - I don't know yet if that is possible with eTechnologia.xxx and has any legal problems).
>Cetin