1. RE: Back to Bach
- Posted by kbochert at copper.net
Feb 20, 2003
-------Phoenix-Boundary-07081998-
Hi SR.Williamson, you wrote on 2/19/03 11:57:38 AM:
>
>Haven't been keeping up with Eu much recently. Am I correct in
>understanding that Bach is dead=3F
>
I view Bach as an evoutionary dead-end and have pretty much ceased
further development.
>
>Not that I could get it to run anyway,
>
In about 40 downloads, I got not a single complaint, even
though I later discovered that they were non-functional.
I believe that the version now at catexa.com works. While
development has stopped, I do intend to leave it functional
so let me know.
> but I was very much interested in
>trying it out - it had a couple of features I was very interested in
>seeing in Eu.
>
>One thing it did not have though, is the ability to bind to the Bach
>interpreter. Was this a problem with the licensing of the source=3F
>
Yes indeed. The source license prevents the buyer from adding
any features that duplicate or compete with the non-free features
of Euphoria.
>Is it
>necessarily fatal, IOW, isn't there some way of licensing that could be
>worked out so that some variations of the Eu interpreter could be sold=3F
>
The variations can be sold, but they are forever prohibited from binding,
tracing, profiling, or translating.
The final straw for Bach was the discovery that 'tracing' includes all
forms of debugging.
Karl Bochert
-------Phoenix-Boundary-07081998---
2. RE: Back to Bach
- Posted by rforno at tutopia.com
Feb 20, 2003
Karl:
Will you please comment on the intended features of Bell?
Regards.
----- Original Message -----
From: <kbochert at copper.net>
Subject: Re: Back to Bach
KAT wrote on 2/19/03 2:37:47 PM:
>It's now known as BLISS.
>Then that was discontinued too.
>
Actually it started as Bliss, then changed to Bach on the
discovery that there were several Bliss's already.
>I'd love to have the source, so i can see how
>Karl did his magic, i have the official RDS source already.
Given that development has ceased, I am now willing to give away
the source to purchasers of Bach. Unfortunately, I am uncertain how
to verify purchase of RDS source, securely transmit it, or what to
say in a license.
>And with debugging, stepping thru code line by line with the interpreter,
>etc? I still like the olde TurboPascal IDE.
>
I have, foolishly, begun sporadic work my own new interpreter. It will have
all new code, and while it was originally intended to be able to run
Euphoria programs, it has evolved into something substantially different.
( The moment you accept one incompatibiity, others flood in!).
It is tentatively named Bell (The icon is a 'not-equals' sign -- does
anyone know why?).
The addition of an IDE/Debugger is one of the prime reasons for taking
on this labor.
Karl
==^^===============================================================
This email was sent to: rforno at tutopia.com
TOPICA - Start your own email discussion group. FREE!
3. RE: Back to Bach
- Posted by gertie at visionsix.com
Feb 20, 2003
On 20 Feb 2003, at 0:56, rforno at tutopia.com wrote:
>
> Karl:
> Will you please comment on the intended features of Bell?
Please.
I have done a good bit of mirc scripting the last two weeks, but no Eu code.
No, mirc isn't perfect, but neither is Eu. I'd pay a lot more to see the two
blended together, but i said that years ago.
I have the flu and a fever, mirc is easier.
Kat
4. RE: Back to Bach
- Posted by kbochert at copper.net
Feb 20, 2003
-------Phoenix-Boundary-07081998-
You wrote on 2/19/03 8:54:57 PM:
>>
>>Karl:
>> Will you please comment on the intended features of Bell=3F
>>
The driving goal is that Bell should be a language for amateurs.
It should be powerful but not obscure or surprising.
Speed is very important.
>Please.
>I have done a good bit of mirc scripting the last two weeks, but no Eu
>code. No, mirc isn't perfect, but neither is Eu. I'd pay a lot more
> to see the two
>blended together, but i said that years ago.
>
>I have the flu and a fever, mirc is easier.
>
>Kat
>
Can you point me to an address for mirc=3F
Here are some features of my vaporware:
1) Datatypes:
var (object)
int (integer) -- 32-bit, suitable for pointers
real (atom)
list (sequence)
string
class
dictionary -- probably not at first
block=3F=3F -- a block of memory for interfacing with C
2) Classes (like Bach)
3) Exceptions (like Bach)
4) Rigid indentation (like Python)
5) Some keywords
persistant
callback
coroutine
foreach
export
import
rename .. as
goto
continue
exit
6) All subroutines are functions.
The variable '$result' always holds the return value of
the most recently executed function.
7) Function parameters are read-only
8) ... many 'small' features
Perhaps this topic should be on OpenEU=3F=3F
Karl
-------Phoenix-Boundary-07081998---
5. RE: Back to Bach
- Posted by gertie at visionsix.com
Feb 20, 2003
On 19 Feb 2003, at 21:30, kbochert at copper.net wrote:
<snip>
> Can you point me to an address for mirc?
http://www.mirc.com/
The mirror sites are listed there too. The irc-oriented commands are listed at:
http://www.mirc.com/cmds.html
> Here are some features of my vaporware:
>
> 1) Datatypes:
> var (object)
> int (integer) -- 32-bit, suitable for pointers
> real (atom)
> list (sequence)
> string
> class
Multiple inheritances and descendants?
> dictionary -- probably not at first
A Lua thing? Or like a Pascal record?
> block?? -- a block of memory for interfacing with C
Block allocations can be handy, so can pointers. I useto drop a pointer on
top of video memeory, on top of the keybd buffer, onto the ems page, etc, in
dos, in the olden days. An array of char and an array of byte at the same
place saved typecasting back and forth. An array of char on top of a string
type gave me easy indexing. It shouldn't be necessary to do these things,
but like "goto", they can be handy at times.
Kat
6. RE: Back to Bach
Please oh please oh *please* keep the classes as modules feature of
Bach.
That's the entire reason I'm trying to learn Eiffel right now.
