OpenEuphoria

Re: Re help require files

• Posted by rforno at tutopia.com Nov 18, 2001
• 632 views

You have to pay for the feature to create .EXE files. It is not in the
public domain Euphoria. The price is very reasonable, IMHO. Some other
benefits come with this ability: you can shroud the programs, you get a
profiling facility, and run time errors for programs with more than 300
sentences point to the type and place of the error.
You may consult further details in the documents that come with the public
domain version of Euphoria.
----- Original Message -----
From: <galaharsh at rediffmail.com>
To: "EUforum" <EUforum at topica.com>
Subject: Re help require files





hi
i am harsh i am new to euphoria and programming too
i really david, jiri and others for oustanding contribution for the
development for this marvellous language. i welcome you to send me as mu ch
info on programming
      i am currently want to design application such as database , internet
and graphics in dos32 environment.
i would be grateful if some one to send me the files to compile into one EXE
file (Creating standalone applications).

thanking you euphoria users
harsh gala
On Sat, 17 Nov 2001 David Cuny wrote :
>
> Kat wrote:
>
> >> Is there a specific part of the API you are
> referring to?
> >
> > Since the non-portable calls were not named, i was
> looking
> > at them as un-named gotchas.
>
> I asked that poorly. Where on the wxWindows site did it
> talk about the API
> being non-portable?
>
> > But you are making calls to the API of wxwindows, not
> to the
> > OS's API. Where is the wxwindows in the scheme of
> things,
> > imbedded in your wxBasic, or a dll on my machine, or ?
>
> Well, on a conceptual level, wxWindows attempts to map
> calls to the native
> API. So on Windows, it creates native controls (where
> possible), calls
> Windows system functions, etc. On Linux, it calls
> GTK/Motif (it can support
> both libraries, but the Motif port is apparently quite
> rusty) for the GUI,
> and the underlying OS for most of the other stuff.
>
> You can either statically bind the wxWindows library to
> your executable
> (which makes a larger executable) or create a dynamic
> DLL that goes along
> with your application.
>
> Did that answer the question? I'm not sure where
> there's confusion.
>
> -- David Cuny
>
>