OpenEuphoria

Re: Those of us who are C'ly challenged :>

• Posted by Daniel Berstein <daber at PAIR.COM> Jul 16, 1998
• 625 views

-----Original Message-----
De: Nate Brooman <nateb at LOG.ON.CA>
Para: EUPHORIA at cwisserver1.mcs.muohio.edu
<EUPHORIA at cwisserver1.mcs.muohio.edu>
Fecha: Jueves 16 de Julio de 1998 05:39 PM
Asunto: Re: Those of us who are C'ly challenged :>


>Well, one reason Euphoria/Win32 is so weakly developed is because Eu32
>f***ks up the screen.


I have never had this problem.

>One main reason why I think that C is better then Eu is that you can
declare
>stuff below the initial procedure. I.E.:
>
>int main()
>{
>printf("Hello\n");
>goaway();
>}
>
>goaway()
>{
>printf("\nGo away now!\n");
>}
>
>and it's bound to work. But I get errors in Eu by typing:
>
>procedure hello()
>
>  clear_screen()
>  puts(1,"Hello!\n")
>  goaway()
>end procedure
>
>procedure goaway()
>
>  puts(1,"\nGo away now!\n")
>
>end procedure

If you try to compile your C code on a C++ compiler it will complain. Plain
C compilers seems to not need a explicit foward declaration (C++ does need
prototypes for foward calling). I find absolutly more structered to have all
function references be firstly declared. You must agree that Pascal is a
very structured language, and it doesn't support foward calling unless you
explicitly use the "foward" reserved word (at least with Borland's
implementation). If you want an un-structurized language example search for
BASIC (ugghh!!!).

If you read the Euphoria reference manual one of the first things said about
function/procedures is that htey cannot call undeclared (not in scope)
functions/procedures. This oblies you to have your code very well
structured, thinking twice before inserting functions: think (program flow),
then code.

Regards,
    Daniel   Berstein
    daber at pair.com