Re: [xsl] Replacing = with == and ===

It's not about my programming language back ground. It's about so one should 
have consider that in majority of comparing value, we should use == and === for 
comparison. Since in so many language the equal sign(including xml with 
attribute and namespace) is use to assign value. The double equal sign could be 
use to form comparison on an element, it's content and it's attribute. And 
triple equal sign could be use to preform deep comparison; including double 
equal sign comparison and the node's descendants as well.

You can let = stay in for backward compatibility. But including these-==, and 
=== will let up on the confusion. 

Even in xQuery the = prefix with a colon is use to assign value. I'm not 
looking for a debate. Just voicing my frustration.

E-S4L

> On Aug 2, 2014, at 5:06 PM, "L2L 2L emanuelallen(_at_)hotmail(_dot_)com" 
> <xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
>
> I was hoping of a concise read... I am currently reading xQuery, and query 
> xml...
>
> The best one I feel out all that I searched to read was xml quick start. That 
> book is done beautifully and wish for am update, I read it two time ready, 
> and plan on reading it again.
>
> .... The true problem is that no instinct gratification, meaning, I can't 
> just type it into the console and get result. I wish for a console like 
> environment. The reason for me jumping into xml as so is cause of me coming 
> across xqib(a language that can be use for database, server-side, 
> middle-tier, and client side scripting(at least that what the documentation 
> show)) the reason for me tell you this is in hope that you can point me to 
> such an environment for me to practice what I am learning.
>
> Thank you all for the suggestion.... I search for more of a concise reading 
> material but also reading heavy ones to. It just with these thick book, the 
> "I want to learn" is in between concept, and technical detail. Yes that's 
> important. But I wish to just learn the language and what is needed to know. 
> These books to my opinion would sell more if they chop them up into smaller 
> book... I could take these book apart and reorder them and reword them than 
> resell them(but that's not right, and I'm not no wizard to be doing that) a 
> book over a thousand pages could be chop up into five books, each one overing 
> a specific topic. For example; querying xml have mix information that 
> concatenate together, in a chapter they'll give you a little bet of history, 
> syntax, and a discussion view. I do enjoy reading it, but.... "I want to 
> learn!" They could have chop up the book and label as so:
>
>
> -first book
>  querying xml part 1:
> Learning xml, schema, xPath, xslt, and xQuery 
> Pages: 600
>  
> -second book
> querying xml book 2:
> the history of querying data
> Pages: 300
>
> -third book
> querying xml book 3:
> discussions and views on querying xml
> Pages: 300
>
> This instead of over a thousand pages is much better. It allow one to pick a 
> choice what they want to read on. And if please will see toward the other two 
> books to gain more topic. Especially if they had knowledge of it being of one 
> book from the beginning.
>
> I'm writing this in hope of an author of one of these books is reading or get 
> word of this or if someone who is reading this is also reading a fat book and 
> would consider breaking it down into smaller books and making it an series.
>
> Thank you for reading. I got to get back to reading these fat, but enjoyable 
> books... Just think; more books more money... And a little followers waiting 
> on your book to be release... Actually
>
> E-S4L
>
> > On Aug 2, 2014, at 12:01 PM, "Bridger Dyson-Smith 
> > bdysonsmith(_at_)gmail(_dot_)com" 
> > <xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
> >
> > Michael Kay's XSLT 2.0 and XPath 2.0 (for XML, XSLT, and XPath) is some of 
> > the best money I've ever spent on XML-technology-related documentation -- it 
> > is a fantastic piece of work. Mulberry Technologies [1] have an assortment 
> > of print resources available on their website. Ken Holman's Practical 
> > Transformation with XSLT and XPath is another excellent reference [2]. Sal 
> > Mangano's XSLT Cookbook has come in handy for me at various times. 
> >
> > Priscilla Walmsley's XQuery (for XQuery) is a very good introduction to the 
> > language.
> >
> > I'm not sure about a schema reference; the W3 may be a good place to start 
> > [3].
> >
> > While it is not a book, Dmitri Novatchev's XSLT/XPath training course on 
> > Pluralsite is another absolutely excellent resource.
> >
> > HTH,
> > Bridger
> >
> > [1] http://www.mulberrytech.com/
> > [2] http://www.cranesoftwrights.com/training/index.htm#ptux
> > [3] http://www.w3.org/XML/Schema
> >
> >
> >
> > > On Sat, Aug 2, 2014 at 11:22 AM, L2L 2L emanuelallen(_at_)hotmail(_dot_)com 
> > > <xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
> > > .... Anyone know of any good books to read that concentrate mainly on 
> > > teaching xml, xslt, schema, xQuery, and xPath?
> > >
> > > E-S4L
> > >
> > > > On Aug 2, 2014, at 10:03 AM, "Wolfgang Laun 
> > > > wolfgang(_dot_)laun(_at_)gmail(_dot_)com" 
> > > > <xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
> > > >
> > > > To provide you with some unconstrained feedback, I'd like to let you
> > > > know that
> > > >
> > > > (1) proposals to changes to programming languages are best made during
> > > > their development phase, and for XPath and XQuery, that's over (until a
> > > > next revision, if any);
> > > >
> > > > (2) the least you can do is to spell the language(s) correctly, moreover
> > > > the addition of the version you are targeting is essential
> > > >
> > > > (3) any proposed change to the syntax should be unequivocally
> > > > expressed the way syntax is in the original language document, i.e.,
> > > > using EBNF or some such notation, with semantics being expressed
> > > > in clear English,
> > > >
> > > > (4) a proposal for a change should outline the pros and cons, providing
> > > > use cases and the sound rationale, based on experience and a
> > > > solid knowledge of programming languages.
> > > >
> > > > Clearly, to change a programming language that has been around
> > > > for several (more than five) years, with widespread acceptance in
> > > > industry and dozens of tools basing their implementation on the
> > > > established specs, in a fundamental aspect, even if it be a single
> > > > operator, is ludicrous. As you have written that you aren't looking
> > > > for  a response, or expecting a wholehearted no, this raises the
> > > > additional question: cui bono? You've just wasted the time of the
> > > > people following the list.
> > > >
> > > > -W
> > > >
> > > > On 01/08/2014, L2L 2L emanuelallen(_at_)hotmail(_dot_)com
> > > > <xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
> > > > > I feel that cause of the use of attribute using the equal sign, there 
> > > > > should
> > > > > be a change... Or add on that will replace the equal sign in both xPath 
> > > > > and
> > > > > xQuery. To test in a predicated if two nodes are equal; this to my 
> > > > > opinion
> > > > > should be use == and for a deeper test this ===.
> > > > >
> > > > > Thank you for reading. I'm not looking for a respond... Since it'll be a 
> > > > > no.
> > > > > I'm just voicing my opinion on the matter... So please to respond on 
> > > > > telling
> > > > > why not. Don't feel like reading anymore denial.
> > > > >
> > > > > Thank you for reading.
> > > > >
> > > > > E-S4L
> > XSL-List info and archive
> > EasyUnsubscribe (by email)
> XSL-List info and archive
> EasyUnsubscribe (by email)
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--