i think that the "See also" links to array should (all?) be to
arrayOpcodes and so avoid the deprecated array opcode.  Could some one
else confirm this please?

do you mean "fillarray"  instead of "array"?
can you give an example?

	joachim


On 27/05/16 18:48, jpff wrote:
> i think that the "See also" links to array should (all?) be to
> arrayOpcodes and so avoid the deprecated array opcode.  Could some one
> else confirm this please?
> ==John ffitch

>>>>> "joachim" == joachim heintz  writes:

 joachim> do you mean "fillarray"  instead of "array"?
 joachim> can you give an example?

Look at dct, dctinv, col, row.....  Actually I changed them all in git
today as no one seemed interested in either of my posts about this.



 joachim> On 27/05/16 18:48, jpff wrote:
 >> i think that the "See also" links to array should (all?) be to
 >> arrayOpcodes and so avoid the deprecated array opcode.  Could some one
 >> else confirm this please?
 >> ==John ffitch
 >> 

All these pages were created by modifying existing ones. So if there were wrong links in the original, they got multiplied.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 29 May 2016, at 20:19, jpff  wrote:

>>>>>> "joachim" == joachim heintz  writes:
> 
> joachim> do you mean "fillarray"  instead of "array"?
> joachim> can you give an example?
> 
> Look at dct, dctinv, col, row.....  Actually I changed them all in git
> today as no one seemed interested in either of my posts about this.
> 
> 
> 
> joachim> On 27/05/16 18:48, jpff wrote:
>>> i think that the "See also" links to array should (all?) be to
>>> arrayOpcodes and so avoid the deprecated array opcode.  Could some one
>>> else confirm this please?
>>> ==John ffitch
> 
> 

sorry i see no manual page for dct, dctinv, col, row.... — but probably 
your question was meant to someone who knows what this means.

	joachim


On 29/05/16 21:19, jpff wrote:
>>>>>> "joachim" == joachim heintz  writes:
>
>   joachim> do you mean "fillarray"  instead of "array"?
>   joachim> can you give an example?
>
> Look at dct, dctinv, col, row.....  Actually I changed them all in git
> today as no one seemed interested in either of my posts about this.
>
>
>
>   joachim> On 27/05/16 18:48, jpff wrote:
>   >> i think that the "See also" links to array should (all?) be to
>   >> arrayOpcodes and so avoid the deprecated array opcode.  Could some one
>   >> else confirm this please?
>   >> ==John ffitch
>   >>
>
>
> ==John ffitch

Sorry typed o the phoe.

Change made in
c2r.xml
cmplxprod.xml
dctinv.xml
dct.xml
fft.xml
fillarray.xml
getcol.xml
getrow.xml
ifft.xml
mags.xml
phs.xml
pol2rect.xml
r2c.xml
rect2pol.xml
rfft.xml
rifft.xml
setcol.xml
setrow.xml
shiftin.xml
shiftout.xml
unwrap.xml
window.xml

On Sun, 29 May 2016, joachim heintz wrote:

> sorry i see no manual page for dct, dctinv, col, row.... — but probably your 
> question was meant to someone who knows what this means.
>
> 	joachim
>
>
> On 29/05/16 21:19, jpff wrote:
>>>>>>> "joachim" == joachim heintz  writes:
>>
>>   joachim> do you mean "fillarray"  instead of "array"?
>>   joachim> can you give an example?
>> 
>> Look at dct, dctinv, col, row.....  Actually I changed them all in git
>> today as no one seemed interested in either of my posts about this.
>> 
>> 
>>
>>   joachim> On 27/05/16 18:48, jpff wrote:
>>   >> i think that the "See also" links to array should (all?) be to
>>   >> arrayOpcodes and so avoid the deprecated array opcode.  Could some one
>>   >> else confirm this please?
>>   >> ==John ffitch
>>   >>
>> 
>> 
>> ==John ffitch
>> 
>

yes, definitely right and an important fix.

by the way, the "see also" section in nearly all manpages would need a 
hero to go through and to add links to related opcodes.  (most of the 
current ones are not really satisfying.)  this could be a huge help for 
users, and a nice way to surf through the 1,5k (or 1,5m?) world of 
opcodes ... but so much work ...

	joachim


On 30/05/16 16:32, jpff wrote:
> Sorry typed o the phoe.
>
> Change made in
> c2r.xml
> cmplxprod.xml
> dctinv.xml
> dct.xml
> fft.xml
> fillarray.xml
> getcol.xml
> getrow.xml
> ifft.xml
> mags.xml
> phs.xml
> pol2rect.xml
> r2c.xml
> rect2pol.xml
> rfft.xml
> rifft.xml
> setcol.xml
> setrow.xml
> shiftin.xml
> shiftout.xml
> unwrap.xml
> window.xml
>
> On Sun, 29 May 2016, joachim heintz wrote:
>
>> sorry i see no manual page for dct, dctinv, col, row.... — but
>> probably your question was meant to someone who knows what this means.
>>
>>     joachim
>>
>>
>> On 29/05/16 21:19, jpff wrote:
>>>>>>>> "joachim" == joachim heintz  writes:
>>>
>>>   joachim> do you mean "fillarray"  instead of "array"?
>>>   joachim> can you give an example?
>>>
>>> Look at dct, dctinv, col, row.....  Actually I changed them all in git
>>> today as no one seemed interested in either of my posts about this.
>>>
>>>
>>>
>>>   joachim> On 27/05/16 18:48, jpff wrote:
>>>   >> i think that the "See also" links to array should (all?) be to
>>>   >> arrayOpcodes and so avoid the deprecated array opcode.  Could
>>> some one
>>>   >> else confirm this please?
>>>   >> ==John ffitch
>>>   >>
>>>
>>>
>>> ==John ffitch
>>>

I do some when I notice but so many opcodes to read....


On Mon, 30 May 2016, joachim heintz wrote:

> yes, definitely right and an important fix.
>
> by the way, the "see also" section in nearly all manpages would need a hero 
> to go through and to add links to related opcodes.  (most of the current ones 
> are not really satisfying.)  this could be a huge help for users, and a nice 
> way to surf through the 1,5k (or 1,5m?) world of opcodes ... but so much work 
> ...
>
> 	joachim
>
>
> On 30/05/16 16:32, jpff wrote:
>> Sorry typed o the phoe.
>> 
>> Change made in
>> c2r.xml
>> cmplxprod.xml
>> dctinv.xml
>> dct.xml
>> fft.xml
>> fillarray.xml
>> getcol.xml
>> getrow.xml
>> ifft.xml
>> mags.xml
>> phs.xml
>> pol2rect.xml
>> r2c.xml
>> rect2pol.xml
>> rfft.xml
>> rifft.xml
>> setcol.xml
>> setrow.xml
>> shiftin.xml
>> shiftout.xml
>> unwrap.xml
>> window.xml
>> 
>> On Sun, 29 May 2016, joachim heintz wrote:
>> 
>>> sorry i see no manual page for dct, dctinv, col, row.... — but
>>> probably your question was meant to someone who knows what this means.
>>>
>>>     joachim
>>> 
>>> 
>>> On 29/05/16 21:19, jpff wrote:
>>>>>>>>> "joachim" == joachim heintz  writes:
>>>>
>>>>   joachim> do you mean "fillarray"  instead of "array"?
>>>>   joachim> can you give an example?
>>>> 
>>>> Look at dct, dctinv, col, row.....  Actually I changed them all in git
>>>> today as no one seemed interested in either of my posts about this.
>>>> 
>>>> 
>>>>
>>>>   joachim> On 27/05/16 18:48, jpff wrote:
>>>>   >> i think that the "See also" links to array should (all?) be to
>>>>   >> arrayOpcodes and so avoid the deprecated array opcode.  Could
>>>> some one
>>>>   >> else confirm this please?
>>>>   >> ==John ffitch
>>>>   >>
>>>> 
>>>> 
>>>> ==John ffitch
>>>> 
>>> 
>

yes ...

On 30/05/16 22:15, jpff wrote:
> I do some when I notice but so many opcodes to read....
>
>
> On Mon, 30 May 2016, joachim heintz wrote:
>
>> yes, definitely right and an important fix.
>>
>> by the way, the "see also" section in nearly all manpages would need a
>> hero to go through and to add links to related opcodes.  (most of the
>> current ones are not really satisfying.)  this could be a huge help
>> for users, and a nice way to surf through the 1,5k (or 1,5m?) world of
>> opcodes ... but so much work ...
>>
>>     joachim
>>
>>
>> On 30/05/16 16:32, jpff wrote:
>>> Sorry typed o the phoe.
>>>
>>> Change made in
>>> c2r.xml
>>> cmplxprod.xml
>>> dctinv.xml
>>> dct.xml
>>> fft.xml
>>> fillarray.xml
>>> getcol.xml
>>> getrow.xml
>>> ifft.xml
>>> mags.xml
>>> phs.xml
>>> pol2rect.xml
>>> r2c.xml
>>> rect2pol.xml
>>> rfft.xml
>>> rifft.xml
>>> setcol.xml
>>> setrow.xml
>>> shiftin.xml
>>> shiftout.xml
>>> unwrap.xml
>>> window.xml
>>>
>>> On Sun, 29 May 2016, joachim heintz wrote:
>>>
>>>> sorry i see no manual page for dct, dctinv, col, row.... — but
>>>> probably your question was meant to someone who knows what this means.
>>>>
>>>>     joachim
>>>>
>>>>
>>>> On 29/05/16 21:19, jpff wrote:
>>>>>>>>>> "joachim" == joachim heintz  writes:
>>>>>
>>>>>   joachim> do you mean "fillarray"  instead of "array"?
>>>>>   joachim> can you give an example?
>>>>>
>>>>> Look at dct, dctinv, col, row.....  Actually I changed them all in git
>>>>> today as no one seemed interested in either of my posts about this.
>>>>>
>>>>>
>>>>>
>>>>>   joachim> On 27/05/16 18:48, jpff wrote:
>>>>>   >> i think that the "See also" links to array should (all?) be to
>>>>>   >> arrayOpcodes and so avoid the deprecated array opcode.  Could
>>>>> some one
>>>>>   >> else confirm this please?
>>>>>   >> ==John ffitch
>>>>>   >>
>>>>>
>>>>>
>>>>> ==John ffitch
>>>>>
>>>>