Hi,
during a bug-hunting session which will lead to an update of py4gretl
shortly I came across the following quirks and issues in gretl (with Win
snapshot Apr 17):
1) x = (obs>1991:1) isn't working ("expected ')' but found ':'" or
something like that -- this is with quarterly data).
2) In a "ne
On Thu, 26 Apr 2007, Sven Schreiber wrote:
> 1) x = (obs>1991:1) isn't working ("expected ')' but found ':'" or
> something like that -- this is with quarterly data).
(obs>"1991:1") will work. I'll see if I can avoid the need for
the quotes.
> 2) In a "new variable" dialog, x=0 produces scalar
Allin Cottrell schrieb:
> On Thu, 26 Apr 2007, Sven Schreiber wrote:
>
>> 1) x = (obs>1991:1) isn't working ("expected ')' but found ':'" or
>> something like that -- this is with quarterly data).
>
> (obs>"1991:1") will work. I'll see if I can avoid the need for
> the quotes.
Maybe it's enoug
On Thu, 26 Apr 2007, Sven Schreiber wrote:
> >> 7) Is there any way to start gretl with a console window showing error
> >> messages on Windows?
> >
> > Not that I'm aware of; I'll try researching that -- I agree it
> > would be useful.
>
> Well that could be something where I could actually h
Allin Cottrell schrieb:
> On Thu, 26 Apr 2007, Sven Schreiber wrote:
>
7) Is there any way to start gretl with a console window showing error
messages on Windows?
>>> Not that I'm aware of; I'll try researching that -- I agree it
>>> would be useful.
>> Well that could be something whe
On Mon, 30 Apr 2007, Sven Schreiber wrote:
> > This is completely untested -- but the snapshot I'm putting in
> > place right now has a new -g or --debug command-line option for
> > gretlw32.exe. This is intended to send stdout and stderr to a
> > console window.
> >
>
> Well thanks, but it's
