OpenEuphoria

Re: Newbies - a proposal

• Posted by Brian Broker <bkb at cnw.com> Sep 22, 2004
• 439 views

Kat wrote:
> 
> On 22 Sep 2004, at 14:07, Patrick Barnes wrote:
> 
> > > I consider how to use the language, and what it can do, to be far more
> > > important than how to set up to run it. Setup is a one-time event, a easy
> > > setup on a(nother) language that cannot do anything isn't worth the read.
> > 
> > That is true... However if someone can't even set the development
> > environemt up, they're not going to get to programming. Rob, I really
> > think you ought to automate this a bit more...
> 
> Lemme try again.... if i don't see the howto of a language, an example of how 
> the words are used, and what the language words are, i won't bother to 
> download the language. Presto, no setup. I haveto be already interested in a 
> language to download a language with no online help, with all the docs in the 
> download/install package.
> 
> And win/dos isn't that nice about installing anyhow, what with the rebooting 
> and fixed paths and such. I deleted the Eu-specific lines in autoexec, and 
> just copy a /bin dir everywhere i go.
> 
> Kat
> 

Ouch! Do you do that with every programming environment you use?  If rebooting 
is an issue then why not just create a batch file to do the minimal environment
setup?

For example:
-- start file Euphoria.bat --

REM -- launch a command prompt for Euphoria programming

REM -- add euphoria\bin to your path
PATH=%PATH%;C:\EUPHORIA\BIN

REM -- add EUDIR environment variable
EUDIR=C:\EUPHORIA

REM -- add EUINC environment variable, for example:
EUINC=C:\EUPHORIA\INCLUDE\Win32Lib\Include;C:\EUPHORIA\INCLUDE\EuAllegro

-- end Euphoria.bat --

Now double-click Euphoria.bat and presto!

Just a thought, no flames required...
-- Brian