1. Re[2]: Euphoria 2.5 alpha
- Posted by akusaya at gmx.net
Nov 17, 2004
>> 6. Bug: 2.5 exw.exe doesn't close the source file after parsing
>> program, while 2.4 does. For example exw.exe program.exw. While
>> program.exw is running, file program.exw is still open!
K> I've been complaining of that for years in 2.3.
In 2.3? You mean the bug exist in 2.3, fixed in 2.4, and comes again
in 2.5?
2. Re: Re[2]: Euphoria 2.5 alpha
On 17 Nov 2004, at 16:28, akusaya at gmx.net wrote:
>
> >> 6. Bug: 2.5 exw.exe doesn't close the source file after parsing
> >> program, while 2.4 does. For example exw.exe program.exw. While
> >> program.exw is running, file program.exw is still open!
>
> K> I've been complaining of that for years in 2.3.
>
> In 2.3? You mean the bug exist in 2.3, fixed in 2.4, and comes again
> in 2.5?
No, since i didn't get 2.4, i don't know that it was fixed.
Kat
3. Re: Re[2]: Euphoria 2.5 alpha
Kat wrote:
>
> On 17 Nov 2004, at 16:28, akusaya at gmx.net wrote:
>
> >
> > >> 6. Bug: 2.5 exw.exe doesn't close the source file after parsing
> > >> program, while 2.4 does. For example exw.exe program.exw. While
> > >> program.exw is running, file program.exw is still open!
> >
> > K> I've been complaining of that for years in 2.3.
> >
> > In 2.3? You mean the bug exist in 2.3, fixed in 2.4, and comes again
> > in 2.5?
>
> No, since i didn't get 2.4, i don't know that it was fixed.
>
>
You were complaining and then when the solution to your complaint was released,
you ignored it and kept complaining? Some people really do just like to
complain...
4. Re: Re[2]: Euphoria 2.5 alpha
On 17 Nov 2004, at 1:17, Andy Serpa wrote:
>
>
> posted by: Andy Serpa <ac at onehorseshy.com>
>
> Kat wrote:
> >
> > On 17 Nov 2004, at 16:28, akusaya at gmx.net wrote:
> >
> > >
> > > >> 6. Bug: 2.5 exw.exe doesn't close the source file after parsing
> > > >> program, while 2.4 does. For example exw.exe program.exw. While
> > > >> program.exw is running, file program.exw is still open!
> > >
> > > K> I've been complaining of that for years in 2.3.
> > >
> > > In 2.3? You mean the bug exist in 2.3, fixed in 2.4, and comes again
> > > in 2.5?
> >
> > No, since i didn't get 2.4, i don't know that it was fixed.
> >
> >
> You were complaining and then when the solution to your complaint was
> released,
> you ignored it and kept complaining? Some people really do just like to
> complain...
Golly forking gee, i was trying to keep my a$$ out of jail. Perhaps you don't
understand, but i have spent FAR more on legal fees and lawyers because a
neighbor turned attack dogs loose on me, and i had to shoot one before it
could kill me. I am out far more $ than i could have spent on Euphoria. I can't
put up a dsl tower now because of the danmed neighbor and his dog. Or
upgrade the computer. Or repair the car, or put up a fence, or have heat this
winter. And the charge for defending myself is a felony.
Kat
5. Re[2]: Euphoria 2.5 alpha
- Posted by akusaya at gmx.net
Nov 18, 2004
>> 3. I'm still confused about .il files. How to produce (unshrouded) .il
>> files?
R> The binder/shrouder will produce shrouded .il files
R> that can be read by backend.exe etc.
R> There is no way to produce an unshrouded .il file.
You said it's proprietary? But the code to make IL files is in emit.e,
isn't it? And the byte codes is in reswords.e, right? So it looks like
we can make .il files using the source code. Am I correct?
Can the eu.ex run .il files?
R> in this respect (though how many people want to modify the
R> very source file they are currently running?)
Me too. Nearly always.
6. Re: Re[2]: Euphoria 2.5 alpha
Akusaya wrote:
> >> 3. I'm still confused about .il files. How to produce (unshrouded) .il
> >> files?
>
> R> The binder/shrouder will produce shrouded .il files
> R> that can be read by backend.exe etc.
> R> There is no way to produce an unshrouded .il file.
>
> You said it's proprietary? But the code to make IL files is in emit.e,
> isn't it? And the byte codes is in reswords.e, right? So it looks like
> we can make .il files using the source code. Am I correct?
You can dump the IL codes into a file of your own design,
but backend.exe will not understand that file.
> Can the eu.ex run .il files?
No.
In order to sell the Binder, I can only allow my Binder
to bind something onto my (fast) backend. That's why the .il
format is proprietary. If someone wants to make their
own binder, that somehow binds with eu.ex or execute.e,
that's fine, but it will yield a larger, much slower .exe file.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
7. Re: Re[2]: Euphoria 2.5 alpha
[snip]
> In order to sell the Binder, I can only allow my Binder
> to bind something onto my (fast) backend. That's why the .il
> format is proprietary. If someone wants to make their
> own binder, that somehow binds with eu.ex or execute.e,
> that's fine, but it will yield a larger, much slower .exe file.
But maybe the ones who have bought the binder could be able to run
IL code generated by the euphoria frontend with the c backend?
Regards, Alexander Toresson
Shhh! Be vewy quiet! I'm hunting wuntime ewwows!
