From andreas.rosenblad@ltv.se Wed Jan 28 09:02:19 2009
From: andreas.rosenblad@ltv.se
To: gretl-devel@gretlml.univpm.it
Subject: [Gretl-devel] regarding the new modprint command...
Date: Wed, 28 Jan 2009 15:02:12 +0100
Message-ID: <OFBBAC8289.473FC52D-ONC125754C.004CAEF2-C125754C.004D12B3@ltv.se>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2367009549726655252=="

--===============2367009549726655252==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit



Regarding the new modprint command...

Rlease
1. Document it in the user's manual.
2. Add it as a recognised highlighted command in script files (e.g. mark it
with brown just as the print and printf commands).

Best regards
Andreas


--===============2367009549726655252==--


From r.lucchetti@univpm.it Wed Jan 28 18:13:43 2009
From: Riccardo (Jack) Lucchetti <r.lucchetti@univpm.it>
To: gretl-devel@gretlml.univpm.it
Subject: Re: [Gretl-devel] regarding the new modprint command...
Date: Thu, 29 Jan 2009 00:13:41 +0100
Message-ID: <alpine.DEB.1.10.0901290012070.15209@ec-4.econ.univpm.it>
In-Reply-To: OFBBAC8289.473FC52D-ONC125754C.004CAEF2-C125754C.004D12B3@ltv.se
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4671107414861949101=="

--===============4671107414861949101==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

On Wed, 28 Jan 2009, andreas.rosenblad(a)ltv.se wrote:

>
>
> Regarding the new modprint command...
>
> Rlease
> 1. Document it in the user's manual.

A brief description is already in the reference manual and in the online 
help. But you're right, an example would be helpful.

> 2. Add it as a recognised highlighted command in script files (e.g. mark it
> with brown just as the print and printf commands).

Hmmm... this should already happen. It does work here.


Riccardo (Jack) Lucchetti
Dipartimento di Economia
Università Politecnica delle Marche

r.lucchetti(a)univpm.it
http://www.econ.univpm.it/lucchetti

--===============4671107414861949101==--


From r.lucchetti@univpm.it Wed Jan 28 18:37:15 2009
From: Riccardo (Jack) Lucchetti <r.lucchetti@univpm.it>
To: gretl-devel@gretlml.univpm.it
Subject: Re: [Gretl-devel] regarding the new modprint command...
Date: Thu, 29 Jan 2009 00:37:13 +0100
Message-ID: <alpine.DEB.1.10.0901290034080.15209@ec-4.econ.univpm.it>
In-Reply-To: alpine.DEB.1.10.0901290012070.15209@ec-4.econ.univpm.it
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7354211731790058365=="

--===============7354211731790058365==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

On Thu, 29 Jan 2009, Riccardo (Jack) Lucchetti wrote:

> On Wed, 28 Jan 2009, andreas.rosenblad(a)ltv.se wrote:
>
>> 
>> 
>> Regarding the new modprint command...
>> 
>> Rlease
>> 1. Document it in the user's manual.
>
> A brief description is already in the reference manual and in the online 
> help. But you're right, an example would be helpful.

Have a look here:

<script>
set echo off
set messages off

function my_own_ols(series y, series x)
     s2 = 1
     b0 = 0
     b1 = 0

     mle ll = -0.5*(ln(s2) + e^2/s2)
         series e = y - b0 - b1*x
         params b0 b1 s2
     end mle -q

     printf "\n  ------ My own ols (via ML!) --------------------------"
     table = $coeff ~ $stderr
     table = table[1:2,]
     names = "constant,x,sigma"
     matrix sigma = sqrt(s2)
     modprint table names sigma
end function

nulldata 10
set seed 12345
x = normal()
y = normal()
ols y 0 x --simple-print
my_own_ols(y,x)
</script>

Is this too silly to package as a practice .inp file? Or maybe it could 
find its way to the User's Manual?



Riccardo (Jack) Lucchetti
Dipartimento di Economia
Università Politecnica delle Marche

r.lucchetti(a)univpm.it
http://www.econ.univpm.it/lucchetti

--===============7354211731790058365==--


From cottrell@wfu.edu Wed Jan 28 20:37:38 2009
From: Allin Cottrell <cottrell@wfu.edu>
To: gretl-devel@gretlml.univpm.it
Subject: Re: [Gretl-devel] regarding the new modprint command...
Date: Wed, 28 Jan 2009 20:37:38 -0500
Message-ID: <Pine.A41.4.58.0901282036330.315682@f1n11.sp2net.wfu.edu>
In-Reply-To: alpine.DEB.1.10.0901290012070.15209@ec-4.econ.univpm.it
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8533956489947749490=="

--===============8533956489947749490==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Thu, 29 Jan 2009, Riccardo (Jack) Lucchetti wrote:

> On Wed, 28 Jan 2009, andreas.rosenblad(a)ltv.se wrote:
> >
> > Regarding the new modprint command...
> >
> > Rlease
> > 1. Document it in the user's manual.
>
> A brief description is already in the reference manual and in the online
> help. But you're right, an example would be helpful.
>
> > 2. Add it as a recognised highlighted command in script files (e.g. mark it
> > with brown just as the print and printf commands).
>
> Hmmm... this should already happen. It does work here.

And it works here too.  Andreas, what version of gretl are you
running?

Allin.

--===============8533956489947749490==--


From andreas.rosenblad@ltv.se Thu Jan 29 04:22:05 2009
From: andreas.rosenblad@ltv.se
To: gretl-devel@gretlml.univpm.it
Subject: Re: Re: [Gretl-devel] regarding the new modprint command...
Date: Thu, 29 Jan 2009 10:22:01 +0100
Message-ID: <OF060B7DB8.5D3EE7BC-ONC125754D.003339A4-C125754D.00336BFC@ltv.se>
In-Reply-To: Pine.A41.4.58.0901282036330.315682@f1n11.sp2net.wfu.edu
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5963803827666670996=="

--===============5963803827666670996==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit


gretl-devel-bounces(a)lists.wfu.edu skrev 2009-01-29 02:37:38 :

> On Thu, 29 Jan 2009, Riccardo (Jack) Lucchetti wrote:

> > On Wed, 28 Jan 2009, andreas.rosenblad(a)ltv.se wrote:
> > >
> > > Regarding the new modprint command...
> > >
> > > Rlease
> > > 1. Document it in the user's manual.
> >
> > A brief description is already in the reference manual and in the
online
> > help. But you're right, an example would be helpful.
> >
> > > 2. Add it as a recognised highlighted command in script files
> (e.g. mark it
> > > with brown just as the print and printf commands).
> >
> > Hmmm... this should already happen. It does work here.

> And it works here too.  Andreas, what version of gretl are you
> running?

Version 1.8.0 build date 2009-01-26 on Windows XP.

Andreas


--===============5963803827666670996==--


From cottrell@wfu.edu Thu Jan 29 17:18:41 2009
From: Allin Cottrell <cottrell@wfu.edu>
To: gretl-devel@gretlml.univpm.it
Subject: Re: Re: [Gretl-devel] regarding the new modprint command...
Date: Thu, 29 Jan 2009 17:18:40 -0500
Message-ID: <Pine.A41.4.58.0901291716250.405922@f1n11.sp2net.wfu.edu>
In-Reply-To: OF060B7DB8.5D3EE7BC-ONC125754D.003339A4-C125754D.00336BFC@ltv.se
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3311220143361673432=="

--===============3311220143361673432==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Thu, 29 Jan 2009 andreas.rosenblad(a)ltv.se wrote:

> > And it works here too.  Andreas, what version of gretl are you
> > running?
>
> Version 1.8.0 build date 2009-01-26 on Windows XP.

Ah, I see: the modprint help item is there OK, but the Windows
version of the XML file that causes commands to be highlighted in
the script window was not up to date (the mechanism for
auto-updating that file was not working).  Now fixed.

Allin.

--===============3311220143361673432==--