Re: Interpreter for old basic programs from the line number era

On 11 Mrz., 18:21, "Auric__" <not.my.r...@[EMAIL PROTECTED]
> wrote:
> On Sat, 08 Mar 2008 09:20:26 GMT,  wrote:
> > On 7 Mrz., 18:12, "Auric__" <not.my.r...@[EMAIL PROTECTED]
> wrote:
> >> On Thu, 06 Mar 2008 20:05:46 GMT,  wrote:
>
> >> (FYI, took a bit over 6 minutes to d/l your 964 kib file.)
> > So you actually managed to download it. Did your compile succeed?
> > Do you have any comments about Bas7 (or the other examples)?
> > I really need any feedback I can get.
>
> The compile went fine. I had to edit the makefile to point at my libXll,
> because the X11 lib dir isn't in $PATH, and isn't the same as what you
> have in yours (mine is /usr/X11R6/lib, with links in /usr/lib/X11 and
> /usr/X11/lib).

Maybe I should add some code to 'make depend' which finds out
where the X11 lib is. A ./configure script would probably be
the right solution. But until now I have not used ./configure
since it works only on unix inspired operating systems.

> During the compile there were *many* warnings about
> parameters being passed as different types due to prototypes (mostly
> double -> float and signed/unsigned) but no errors.
>
> I ran a few sample programs (castle.sd7 brought back some fond memories
> of swearing at the screen because I'd just been killed again). I ran
> about a dozen old BASICA/GWBASIC sample programs through bas7 without
> any obvious errors, but with most of them it was kinda hard to tell, and
> the logs often weren't of any help.

Error messages in bas7.log start with ' ***** ' (without the
quotes). Do you have suggestions to make the logs more
helpful?

> I have 2 suggestions and a question:
> 1) Add some way to pause at the end of a bas7 program without
> specifically adding a pause to the .bas file.

Since some programs need this, while in other programs
it is not useful, it IMHO cannot be done automatically.
I think an option for Bas7 would be the solution for that.

> 2) For .sd7 programs that open a new window (such as castle.sd7) add a
> way to keep that window open after the end of the script.

Why should a window stay open when the program is finished?
What do you want to do with such an open window?
Did the program quit without giving you a chance to see the
reason for it?
That would be a bug in castle.sd7 and not in the interpreter.
I thought that the castle.sd7 program asks for confirmation
before it ends (and the interpreter removes all its windows).

> q) I notice that bas7 apparently doesn't support MS-style colors. Are
> colors supported at all?

Colors are supported in graphic programs (the graphic support
is not finished: YMMV). The various unix consoles do not
really have a guaranteed color support. Therefore the Seed7
text output at the console does not have color support.
But in Seed7 there are emulated text consoles in a graphic
window. This text consoles have also color support. Until now
I do not use this feature for Bas7. I will look at it.

Greetings Thomas Mertes

Seed7 Homepage:  http://seed7.sourceforge.net
Seed7 - The extensible programming language: User defined statements
and operators, abstract data types, templates without special
syntax, OO with interfaces and multiple dispatch, statically typed,
interpreted or compiled, portable, runs under linux/unix/windows.