Xsl

[DimPrawn]

Lookup Muenchian Technique

[AtW]

I've come across with some people mentioning it: it seems to relate to groupings that I do in DB using SQL stored procedure that has not got stupid limitation of a "functional" language.

Not sure grouping will help in case of first N rows.

[threaded]

I do not believe it is possible to select FIRST X nodes satisfying given criteria (true in our case) and stop matching immediately after first node that fails such criteria - thus excluding possibly further nodes that satisfy that criteria: prove it otherwise please, I would appreciate it a lot and will shut up about XSL for 24 hours (until I hit some other brick wall).

Now, how does that saying go: "If you only have a hammer, everything begins to look like a nail."

You're looking at it all wrong. How exactly does "FIRST X nodes satisfying given criteria" differ from "break out of a loop"? Which we've already told you is a wrong way of thinking in this language...

[AtW]

threaded - either offer your solution (at least DimPrawn offered one that I actually found myself, though its not ideal due to having to use node-set() which is non-standard extention, leading me to believe its not possible to do that using pure XSL) or feck off.

I am solving real life problems - I don't care if language is called functional or not, if it does the job well then its pretty functional for me, if not, then it disfunctional - something that XSLT is.

[DimPrawn]

With a combination of position() and preceding-sibling()

Something like

@my-value='false' and not(ancestor::*/preceding-sibling::row/entry/@my-value='false')

[AtW]

ok, so this is basically this: select node if:
a) its true (rather than false you used)
AND
b) none of the previous nodes were false?

[threaded]

Well, here is a solution that you may well understand.

Start constructing a variable, inside this iterate through each node, if it has the value put out a 'True', end constructing the variable.

Construct a new variable, if the first four chars of the variable above is 'True', set it to True.

Use the second var as your boolean, as it is either True or null.



threaded in "And I've seen that done. What, in maven? Hush now or you'll upset someone." mode

[Jabberwocky]

threaded - either offer your solution (at least DimPrawn offered one that I actually found myself, though its not ideal due to having to use node-set() which is non-standard extention, leading me to believe its not possible to do that using pure XSL) or feck off.

I am solving real life problems - I don't care if language is called functional or not, if it does the job well then its pretty functional for me, if not, then it disfunctional - something that XSLT is.

It can certainly do the job Atw so it is functional in more than one sense. The question is can you do the job ? If you are not up to it then you are an inferior foreign code imigrant.

Please leave this country and go back to the simple for/next loops of your birth. Real men use ML - it should be on the entrance exams anyway.

[_V_]

I think the penny, may, finally, have dropped

[AtW]

You have not offered the solution - DimPrawn did, even though I strongly suspect that performance will suffer for long sets, but then again I would not use XSL for performance critical operations, even though clearly having small loop that will abort quickly will always be faster - so much for functional way of doing things being better, eh?