[e-lang] a few notes about E install/basic usage

[Kevin Reid]

On Jun 29, 2007, at 13:43, Zooko O'Whielacronx wrote:
>> Please rewrite inst-e.bash to work with the purej distribution --
>> right now, there's a nonworking copy of it included, and that's bad.
>> If you supply a fix I'll commit it.
>
> It currently works, if you do:
>
> mkdir dist
> mv * dist
> mv dist/inst-e.bash .
> ./inst-e.bash
>
> Therefore, we could change inst-e.bash to "cp -a ." instead of "cp - 
> a dist".  Would that satisfy?

I'l try it out.

>>> I finally hit an irritating snag and stopped for now.  This was  
>>> when I wanted to import some E code from a file into the  
>>> interpreter.  To do so, according to Walnut [1], I need to import  
>>> my module as something like <import:com.yourdomain.e.makeQueue>.
>>
>> You can do this:
>>
>> <elang:syntax.EParser>(<file:makeQueue>.getTwine()).eval(safeScope)
>
> Thanks for the tip!  Should this live in the Wiki Walnut so that  
> other folks like me don't get snagged by the Java namespace issue?

Yes; please do.

>>> 4.  After I held my nose and went through the hassle of mkdir "/ 
>>> System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/ 
>>> lib/ext/emakers" and symlink my file so that it is reachable from  
>>> that directory, then it still didn't work.
>>
>> Ack, don't do this. Use the -cpa option to rune instead.
>
> Thanks for the other tip!  I read the output from "rune --help"  
> several times and didn't see this option...  Next time I play with  
> E I'll check if that can be improve somehow.

Note that that option adjusts the Java -classpath option, which  
exists already. Even independent of E-on-Java, there is no reason to  
change system directories in order to add resources.

Also, one of my projects is a 'module' system intended to replace E's  
uses of the Java classpath for application/library loading.

-- 
Kevin Reid                            <http://homepage.mac.com/kpreid/>