Short LINQ syntax
-
I read your proposal and I watched the YouTube video. At the end of it I was no further forward. Throwing phrases like Flex Data Formats Interchange Cross Platforms tells me nothing. Seriously. Write your proposal in English, not technical shorthand. Your refusal to understand that we aren't going to just download a spam posting isn't doing you any favours. Tell you what. Why don't you write an article about this? This is, after all, what CodeProject is all about. If you write an article clearly showing what this solves, you might actually find that people are more receptive. Right now, you're winning no friends here.
:thumbsup:
-
Member 10277067 wrote:
discussion of a new possible concept
Understandable.
Member 10277067 wrote:
discuss about best practices of coding in another post
Not so. If a new concept does not adhere to good or best coding practices, then it will not make it very far since people will be less motivated to using it.
"I've seen more information on a frickin' sticky note!" - Dave Kreskowiak
Very good approach Paul. Just what I want to avoid, a premature disinterest. You can help me in this matter? The project propose a toolkit for data query, mining and transformation across multiple formats strong typed objects, dynamic objects, JSON, XML and CSV to attend many real world companies issues like systems integration, B.I, etc. Awaiting your response. Tks a lot.
-
Member 10277067 wrote:
Write Less, Do More
You keep using these words, I don't think they mean what you think they mean. JQuery allows us to write code that works across browsers, prior to that we had to write different versions of JavaScript for different browsers. JQuery also provides simple ways to do common tasks which would otherwise require a fair amount of JavaScript code. That's what the "write less" part means, it doesn't literally mean to make code as terse as possible. Typing is not a bottleneck in programming (unless you're doing it wrong).
Similar to this, the proposed open-source tool, supports the manipulation of data in various formats JSON, XML and CSV within a short syntax for its use. Tks for your reply :-)
-
Very good approach Paul. Just what I want to avoid, a premature disinterest. You can help me in this matter? The project propose a toolkit for data query, mining and transformation across multiple formats strong typed objects, dynamic objects, JSON, XML and CSV to attend many real world companies issues like systems integration, B.I, etc. Awaiting your response. Tks a lot.
Member 10277067 wrote:
The project propose a toolkit for data query, mining and transformation across multiple formats strong typed objects, dynamic objects, JSON, XML and CSV to attend many real world companies issues like systems integration, B.I, etc.
Attempting to generalize everything is doomed to failure. Either for you or someone that has to clean up the mess.
-
Member 10277067 wrote:
The project propose a toolkit for data query, mining and transformation across multiple formats strong typed objects, dynamic objects, JSON, XML and CSV to attend many real world companies issues like systems integration, B.I, etc.
Attempting to generalize everything is doomed to failure. Either for you or someone that has to clean up the mess.
What are you talking about ?
-
Anyone know this new short syntax method of LINQ queries ? http://bwqs.codeplex.com
-
Read more. Tks ;-)
-
Read more. Tks ;-)
I read
Quote:
The initial idea was to create something similar to Dynamic LINQ using a different strategy to Reflection.Emit , based on class CSharpCodeProvider / CompileAssemblyFromSource , executing methods containing LINQ queries generated at runtime to hold this solution based on logical comparison . As our notorious colleagues on Microsoft ever thought this idea, we extend ourselves from it ! BWQS (BitWise Query Service) is a suggestion to a shorter code when performing Elastic searches on objects, SQL Databases, XML, JSON and CSV files, analogous to the proposal of John Resig with JQuery in 2006 in the html DOM and Javascript context. Think any attribute of an object can be indexed within a binary table defining binary values at runtime to each attribute according to his ordinaridade, we can make comparisons using logical disjunction recursively for these attributes, both as predicates, such as the lambda search criteria. This, together with the concept of postfix representation of the operations, (Reverse Polish Notation Charles Hamblin in 1950).
and I am no wiser. Why?
PooperPig - Coming Soon
-
I read
Quote:
The initial idea was to create something similar to Dynamic LINQ using a different strategy to Reflection.Emit , based on class CSharpCodeProvider / CompileAssemblyFromSource , executing methods containing LINQ queries generated at runtime to hold this solution based on logical comparison . As our notorious colleagues on Microsoft ever thought this idea, we extend ourselves from it ! BWQS (BitWise Query Service) is a suggestion to a shorter code when performing Elastic searches on objects, SQL Databases, XML, JSON and CSV files, analogous to the proposal of John Resig with JQuery in 2006 in the html DOM and Javascript context. Think any attribute of an object can be indexed within a binary table defining binary values at runtime to each attribute according to his ordinaridade, we can make comparisons using logical disjunction recursively for these attributes, both as predicates, such as the lambda search criteria. This, together with the concept of postfix representation of the operations, (Reverse Polish Notation Charles Hamblin in 1950).
and I am no wiser. Why?
PooperPig - Coming Soon
Just a Query Toy, see the samples : http://youtu.be/kLdIS809wBA http://youtu.be/BeFFYMJL9e4 Operations Resume : http://pccs01-001-site1.myasp.net/press Tks ;-)
-
Just a Query Toy, see the samples : http://youtu.be/kLdIS809wBA http://youtu.be/BeFFYMJL9e4 Operations Resume : http://pccs01-001-site1.myasp.net/press Tks ;-)
Well, I read the article (can't watch youtube here) and I still don't understand what the advantage is. Surely writing
var objList = bwq.Query("9>2:2").Where("128::true=");
is so completely and utterly unmaintainable as to render itself useless? I see nothing about the advantage of using this complex and illegible syntax to do what is already available in Linq - so what am I missing?
PooperPig - Coming Soon