Well, SQL is a functional language too (if you ignore the various sublanguages for stored procedures). And I have seem many students struggle with it. They are used to assigning values in loops and the whole concept of SQL is alien to them. But in the end all experienced engineers master it without a problem. (Even though the % of people that can use GroupBy/Having, Window, Cube and outerjoins is tiny). At some point the understand that they *have* to learn, and that just does it.
> On 18 Jun 2015, at 13:39, Ihe Onwuka <[email protected]> wrote: > > > > On Thu, Jun 18, 2015 at 6:23 AM, Ihe Onwuka <[email protected] > <mailto:[email protected]>> wrote: > > > It's how it's presented to the experienced programmer that is the issue. My > metaphor is that an XSLT processor converts an XML document to a stream of > events which you have to write handlers for in the form of template rules. > However that only covers XSLT's push paradigm and although I'd like to say > push is all you need I don't think it's true, sometimes you have to pull. > > I should have added that the processor has built in event handlers so you > only need to write handlers for required functionality that is at variance > with the default for that node type. > > A non-programmer has no problem accepting this but it is alien to the > experienced programmer for processing that he has not explicitly controlled > to occur and it screws them up because they like to step through code with > debuggers. In fact that is often their prime modus operandi > _______________________________________________ > [email protected] > http://x-query.com/mailman/listinfo/talk С уважением, Павел Велихов [email protected]
_______________________________________________ [email protected] http://x-query.com/mailman/listinfo/talk
