OpenEuphoria

Re: .il code/file questions

• Posted by Matt Lewis <matthewwalkerlewis at yahoo.com> Nov 21, 2004
• 661 views

Juergen Luethje wrote:
> 
> Matt Lewis wrote:
> >
> > Basically, you'd have to specify an input format for a pre-il file,
> > including anything that's needed from the front end, and then your
> > code puts it into the format that the backend needs.  You could sell
> > this as part of the binding feature, or even separately.  Then people
> > could distribute their custom code as il files, but anyone who wanted to
> > use the custom language would need to buy your binding package.
> 
> But when people distribute their custom code as EXE files (modified
> standalone Euphoria interpreter), things will look different, if I'm not
> too much confused. So maybe the license should only allow to distribute
> such "customized interpreters" in the form of IL files.

Er...not exactly.  What I'm suggesting is that, as part of the binding
package (or perhaps even separately), Rob provides an analog to 
bind.il.  It takes il code in an "unshrouded" format.  This could be
as simple as (from within the modified front end):

il_file = open( file_name, "w" )
    print( il_file, il_code )
    print( il_file, symtab )
    close(il_file)

Now, instead of bind.il running the frontend on regular Eu source, it
takes the il file and does whatever shrouding it would normally do,
and/or bind it to backend.exe.  The person who does this will have to
own the binder (just like right now).  Anyone else can run the bound
or shrouded code, because it works with backend.exe.  Anyone who wants
to actually work with the modified front end (i.e., its extensions or
new syntax or whatever) would need to buy the binder from Rob.  There's
no new licensing issues.
 
Matt Lewis