Completely agreed. Even within Universe the longer Locate syntax can be
ambiguous.
Tony Gravagno 3xk547...@sneakemail.com wrote in message
news:14130-1347054812-792...@sneakemail.com...
I do the exact opposite for exactly the same reasons. :)
I use the Locate function rather than statement
I have 2 definitive answers. I believe both are true.
I posed the question to the U2-list LinkedIn Pick Users Group (not
Googlegroups).1
No one seemed to know there, either. “Q”uick seemed to be the most
popular guess.
Finally, there were 2 claims of certain knowledge:
Brian Stone says:
On 07/09/12 03:19, Charles Stevenson wrote:
A newbie stumped me: Why are Q-Pointers Q pointers ?
The Q lingo comes from the dawning days of Pick.
Why was the letter Q chosen?
Attribute makes sense.
Synonym makes sense.
PQ for Prestored Query makes sense. PR for Proc
Early versions of Pick did not natively have a way to reference the Master
Dictionary at all. That is, you could not open the master dictionary as a file
because there was no reference to it, to use as the text handle against an OPEN.
This is why the MD itself had a Q pointer called MD, which
...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson
Sent: Friday, September 07, 2012 9:30 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Etymology of Q-Pointer
Early versions of Pick did not natively have a way to reference the Master
Dictionary
-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson
Sent: Friday, September 07, 2012 9:30 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Etymology of Q-Pointer
Early versions of Pick did not natively have a way to reference
I guess it always depends on where you come from and what you know.
I would say the account philosophy is much cleaner than having duplicate
file pointers.
And of course we have accounts in U2 too - it is the working directory.
I have to admit I always hated to work on PI sites - it was not
On 07/09/12 18:28, Mecki Foerthmann wrote:
I guess it always depends on where you come from and what you know.
I would say the account philosophy is much cleaner than having duplicate
file pointers.
And of course we have accounts in U2 too - it is the working directory.
I have to admit I
I have no Idea what you are talking about.
What is wrong with LOCATE A IN B SETTING C ?
On 07/09/2012 20:44, Wols Lists wrote:
On 07/09/12 18:28, Mecki Foerthmann wrote:
I guess it always depends on where you come from and what you know.
I would say the account philosophy is much cleaner than
On 07/09/12 21:44, Mecki Foerthmann wrote:
I have no Idea what you are talking about.
What is wrong with LOCATE A IN B SETTING C ?
Except you've just given me a statement, and I was talking about the
function :-)
The syntax is something like
LOCATE(A,B,1;C)
although as I said, I might have
Much more compact
-Original Message-
From: Wols Lists antli...@youngman.org.uk
To: u2-users u2-users@listserver.u2ug.org
Sent: Fri, Sep 7, 2012 2:11 pm
Subject: Re: [U2] Etymology of Q-Pointer
On 07/09/12 21:44, Mecki Foerthmann wrote:
I have no Idea what you are talking about
and
delete all copies of this message.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wols Lists
Sent: Friday, September 07, 2012 5:11 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Etymology of Q-Pointer
On 07/09
On Fri, Sep 7, 2012 at 2:11 PM, Wols Lists antli...@youngman.org.uk wrote:
On 07/09/12 21:44, Mecki Foerthmann wrote:
I have no Idea what you are talking about.
What is wrong with LOCATE A IN B SETTING C ?
Except you've just given me a statement, and I was talking about the
function :-)
I
I do the exact opposite for exactly the same reasons. :)
I use the Locate function rather than statement because I find it
easier to read and 99% consistent across all platforms.
T
From: John Lorentz
I fully believe that I've never used the function ever since they
introduced
it as an
True about not needing it on PI. But PI could have handled Q-pointers
exactly how UV does today, if they had wanted to.
Personally, I like having 1 F-Pointer and every other pointer a
Q-pointer. Slightly less efficeint, but IMO more manageable.
REPLACE and INSERT functions also allowed (still
The etymology question about Q has deteriorated into a PI vs Pick
discussion.
In the Pick User GoogleGroup, it's about words that rhyme with orange.
No one has the definitive historical answer? I thought maybe our
resident historian, Dawn Wolthuis, would notice my dawning days of
Pick
I agree, Tony. The only time I use the statement is if I need to start a
locate at something other than element 1 (to step through each matching
element) or to locate multiple elements with the located value. Here's
an example:
*
* Method of using LOCATE to find multiple occurrences of value
On 07/09/12 23:14, Charles Stevenson wrote:
True about not needing it on PI. But PI could have handled Q-pointers
exactly how UV does today, if they had wanted to.
Personally, I like having 1 F-Pointer and every other pointer a
Q-pointer. Slightly less efficeint, but IMO more manageable.
A newbie stumped me: Why are Q-Pointers Q pointers ?
The Q lingo comes from the dawning days of Pick.
Why was the letter Q chosen?
Attribute makes sense.
Synonym makes sense.
PQ for Prestored Query makes sense. PR for Proc would have been
better.
D3 User Guide just says,
Charles,
My guess is Quick as in a quick link to another account.
Don Robinson
From: Charles Stevenson stevenson.c...@gmail.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Thursday, September 6, 2012 10:19 PM
Subject: [U2] Etymology of Q-Pointer
A newbie stumped me: Why are Q
20 matches
Mail list logo
