That is the point of the example.
Point taken. But your example holds true whether or not we write x'y or x'*y,
doesn't it?
Said another way, it seems to me that your example illustrates the need for careful
scripting rather than the "right" treatment of x'y vs x'*y. For example,
suppose that I have a script that is designed to compute (1x2)*(2x2)*(2x2), but that an
earlier step produces a 2x1 matrix for the second term. Then as I've written it
(A*B*C) I'd get a possibly misleading result, whereas A*(B*C) would give an error and
cause me to revise my code. Granted, in this example I'd rather have the error.
Going back to Allin's original question (whether gretl's treatment of m1'm2 or
m1'*m2 is "right"), your example illustrates a potential problem when m1 is
'unintentionally' a 1x1 matrix. Are you suggesting that both treatments should
give an error? I'm willing to be persuaded, but that is inconsistent with other
languages.
-----Original Message-----
From: gretl-users-bounces(a)lists.wfu.edu [mailto:gretl-users-bounces@lists.wfu.edu] On
Behalf Of Alan G Isaac
Sent: Friday, December 07, 2012 1:05 PM
To: Gretl list
Subject: Re: [Gretl-users] pre-multiplication by transpose
On 12/7/2012 12:58 PM, Summers, Peter wrote:
But associativity assumes all products are well-defined. A*(B*C) in
your example generates an error because B*C fails.
Indeed.
That is the point of the example.
_______________________________________________
Gretl-users mailing list
Gretl-users(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-users