Ok, before responding to your response (thanks! by the way... it now
makes sense... kinda.. ;) an associate of mine has finally taken me to
task and suggested that, in essence, maybe I should ask if you would
prefer me to call you by your given name, like everyone else, as
opposed to your Doctorate Degree, like no one else (as far as I
personally know, that is) So instead of entering myself into a 12
step program to try and break the habit, maybe I should just ask...
would you prefer if from this point forward I broke the 'habit' if
calling you Dr. Kay or is it something that you don't even give much
In simple explanation, I developed the habit from years back when I
wanted to ensure that you were aware of the fact that I had a
tremendous amount of respect for you. Refering to you as Dr. I felt
showed respect... its that plain and simple. But I do recognize that
it does probably seem a little wierd given that to everyone else you
are Mike and to me Dr. Kay.
I should point out, the reason I am asking this in a public forum as
opposed to a private email is for the simple fact that I know there
are those who are probably confused at times whether to call you Mike
or Dr. Kay, and maybe avoid both because of it. Then again, maybe I
just make a bigger fool of myself... ;)
Anyway, I can recongize now the need for the code, but am still
scratching my head on the 'circularities in variable definitions are
detected statically.' Before I comment further I think I need to
research this as at first take I'm left wondering why?... but then
again, I'm still waiting for that invitation from the W3C to join the
XQuery WG, and am shocked by the fact that it still hasnt arrived.
Maybe you check into that for me? ;) (in case anyone reading this
doesn't realize it, I am MORE than kidding about this... Kind of an
inside joke thats all BUT on the inside, but thats neither here nor
there... I have a HUGE amount of respect for those folks and I know
that at least most of them know it...
Ok, I'm going to try and say it... Thanks for your help Mike!
Wow! That was easier than I thought, although still feels a little
strange.. Depending if and how you respond I will do my best to get
used to it...
On 8/28/05, Michael Kay <mike@...> wrote:
> The April 2005 draft of XQuery allows a module to import its own namespac=
> cycles of imports are allowed provided the modules in the cycle all share
> the same namespace. This feature wasn't implemented in Saxon 8.5, but was
> added in 8.5.1. As you observe, it required a surprising amount of code.
> Before, a global variable declaration in XQuery was always processed befo=
> the references to that variable, meaning that a variable reference could =
> bound to its declaration at the time the variable reference was encounter=
> by the parser. With recursive module imports, this is no longer the case,=
> forwards reference chains need to be maintained and fixed up as a separat=
> phase of processing at the end. In addition (unlike XSLT) XQuery mandates
> that circularities in variable definitions are detected statically, so I
> added code to achieve this.
> On the whole XQuery testing is fairly well covered by the XQTS test suite
> recently released by W3C, but I suspect that it doesn't yet have good
> coverage of multiple modules.
> Michael Kay
> > -----Original Message-----
> > From: saxon-help-admin@...
> > [mailto:saxon-help-admin@...] On Behalf Of
> > M. David Peterson
> > Sent: 28 August 2005 21:01
> > To: saxon-help@...
> > Subject: [saxon] New 'Executable' code
> > Dr. Kay,
> > In going through the latest 8.5.1 source and either merging the
> > changes, or flagging the code for testing based off of known issues
> > with differences between the 1.5 JDK and the latest Classpath/IKVM
> > release, I'm finding a ton of updates, fixes, etc... but none in any
> > great significance beyond a dozen lines or so, and even that seems to
> > be the exception.
> > I did however recently run across the updates to the Executable.java
> > file which seem fairly significant in line count, but based on the
> > comments I'm not sure if this is something to take particular note of
> > and to create tests for, or if your comments:
> > /**
> > * Fix up global variables and functions in all query modules.
> > This is done right at the end, because
> > * recursive imports are permitted
> > */
> > suggest more clean-up work than anything else.
> > I apologize for my ignorance on this, but this is not an area of the
> > Saxon source I have spent any time studying. As such, with the
> > extensive increase in the line count I thought it best to clarify.
> > Best regards,
> > --
> > <M:D/>
> > M. David Peterson
> > http://www.xsltblog.com
> > -------------------------------------------------------
> > SF.Net email is Sponsored by the Better Software Conference & EXPO
> > September 19-22, 2005 * San Francisco, CA * Development
> > Lifecycle Practices
> > Agile & Plan-Driven Development * Managing Projects & Teams *
> > Testing & QA
> > Security * Process Improvement & Measurement *
> > http://www.sqe.com/bsce5sf
> > _______________________________________________
> > saxon-help mailing list
> > saxon-help@...
> > https://lists.sourceforge.net/lists/listinfo/saxon-help
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> saxon-help mailing list
M. David Peterson