1. Two things:
[Irv's create and delete]
Is there any reason you need to even create the fourth element? If =
not, then you can avoid the whole deletion process by simply not adding =
it in the first place. For example:
atom elemCtr
sequence dyn_list,...
elemCtr =3D 1
dyn_list =3D {}
...
if elemCtr !=3D n then
dyn_list =3D ...
else
...
elemCtr =3D 0
end if
elemCtr +=3D 1 -- assumes ver. 2.1
[Linux question]
I've been pinpointing some of the seg faults in attempted ports of =
Euphoria to Linux, and thinking of trying to add screen or graphics =
functions. One problem: conio.h that I'm used to using in DOS doesn't =
exist in Linux. And there's no information about screen or graphics =
routines in the GCC manual at Sun's web site. I've looked at termios.h, =
but it's mostly hardware data with no recognizable I/O routines. Does =
anybody know any more about this?
Michael J. Sabal
mjs at osa.att.ne.jp
http://home.att.ne.jp/gold/mjs/index.html
2. Re: Two things:
On Sun, 24 Jan 1999 16:59:57 +-900, Michael Sabal <mjs at OSA.ATT.NE.JP> wrote:
>[Irv's create and delete]
>
> Is there any reason you need to even create the fourth element? If
> not, then you can avoid the whole deletion process by simply not adding it in the
> first place. For example:
Ummm... the list is of undetermined length. In reality it would be a
graphic image with several thousands of points.
>[Linux question]
>
> I've been pinpointing some of the seg faults in attempted ports of
> Euphoria to Linux, and thinking of trying to add screen or graphics functions.
> One problem: conio.h that I'm used to using in DOS doesn't exist in Linux. And
> there's no information about screen or graphics routines in the GCC manual at
> Sun's web site. I've looked at termios.h, but it's mostly hardware data with no
> recognizable I/O routines. Does anybody know any more about this?
>
Take a look at SVGALIB - it comes with most Linux distros.
Irv
3. Re: Two things:
> [Linux question]
> I've been pinpointing some of the seg faults in attempted ports
> of Euphoria to Linux, and thinking of trying to add screen or graphics
> functions. One problem: conio.h that I'm used to using in DOS doesn't
> exist in Linux. And there's no information about screen or graphics
> routines in the GCC manual at Sun's web site. I've looked at termios.h,
> but it's mostly hardware data with no recognizable I/O routines. Does
> anybody know any more about this?
For text screen routines, I was thinking about writing an include that
used escape sequences for screen procedures and functions. The two
terminal types I know I could implement are ANSI and VT100. There might
also be a need to cache the cursor position...
Another problem is get_key and wait_key... Linux doesn't offer these
either, afaik. The only way to get around that is to set up non-blocking
terminal i/o... yuck.
[20 mintutes later]
I found vga.h and friends in my RedHat usr/include. They have it all for
screen, graphics, mouse, keyboard, even joystick. ModeX and SVGA are also
supported. Way cool.
I guess I better fix those seg faults then, huh? 
Later,
_______ ______ _______ ______
[ _ \[ _ ][ _ _ ][ _ ]
[/| [_] |[/| [_\][/ | | \][/| [_\]
| ___/ | _] | | | _]
[\| [/] [\| [_/] [\| |/] [\| [_/]
[_____] [______] [_____] [______]
xseal at harborside.com ICQ:13466657
http://www.harborside.com/home/x/xseal/euphoria/
