Prev: Serial Device comms application architecture
Next: Namespace Problem
From: Bob on 26 May 2010 23:40
On Wed, 26 May 2010 03:20:08 -0700 (PDT), Thes <thesmusic(a)myway.com>
wrote:

>> >So you could do something like (untested):
>>
>> >List<colouredObject> colouredObjectList = ...
>> >...
>> >var results = from c in colourObjectList
>> > � � � � � � �where <some primary condition>
>> > � � � � � � �select c;
>>
>> >if(<some secondary condition>)
>> >{
>> > � �results = results.Where(c => c.size > 12);
>> >}
....
>>
>> Hi Thes,
>>
>> That's what I was referring to above as 'stack of
>> conditional-query-condit-query'.
>
>Ooh - I see! I should RTFMessage properly!

Don't misunderstand--I appreciate your reply. It is probably the exact
way to do that. I initially thought that I was overlooking
something... that there would be some way to do that within one
'unified' query. But then I noticed some code similar to yours in a
Linq book (maybe either Mayo or Marguerie). I was thinking more about
the issue of optimization. The code itself would be much more elegant
if structured as you suggested.

The question of optimization is tough to Google. Difficult to think of
distinct keywords to narrow down something like that. I don't even
know what the 'successive refinement' process above would be called.
First  |  Prev  | 
Pages: 1 2
Prev: Serial Device comms application architecture
Next: Namespace Problem