http://www.heron-language.com/c-sharp-critique.html

"Mark T" <Mark_member@pathlink.com> wrote in message news:bvj7r4$30rl$1@digitaldaemon.com...
> http://www.heron-language.com/c-sharp-critique.html

It's an interesting read. I'd like to know what language the author *does* use, and why.

Walter wrote:

> "Mark T" <Mark_member@pathlink.com> wrote in message
> news:bvj7r4$30rl$1@digitaldaemon.com...
> 
>>http://www.heron-language.com/c-sharp-critique.html
> 
> 
> It's an interesting read. I'd like to know what language the author *does*
> use, and why.
> 
> 

Looks like he made his own: <http://www.heron-language.com/spec.html>

 -- andy

Apparently Heron.  :)

Sean

Walter wrote:
| "Mark T" <Mark_member@pathlink.com> wrote in message
|| http://www.heron-language.com/c-sharp-critique.html
|
| It's an interesting read. I'd like to know what language the author
| *does* use, and why.

"Andy Friesen" <andy@ikagames.com> wrote in message news:bvjkpt$kmp$1@digitaldaemon.com...
> Walter wrote:
>
> > "Mark T" <Mark_member@pathlink.com> wrote in message news:bvj7r4$30rl$1@digitaldaemon.com...
> >
> >>http://www.heron-language.com/c-sharp-critique.html
> > It's an interesting read. I'd like to know what language the author
*does*
> > use, and why.
> Looks like he made his own: <http://www.heron-language.com/spec.html>

I can understand his motivation to do that <g>.

Some good points in there, some of which also apply to D. :(

"Mark T" <Mark_member@pathlink.com> wrote in message news:bvj7r4$30rl$1@digitaldaemon.com...
> http://www.heron-language.com/c-sharp-critique.html
>
>

Walter wrote:
> "Andy Friesen" <andy@ikagames.com> wrote in message
> news:bvjkpt$kmp$1@digitaldaemon.com...
> 
>>Walter wrote:
>>
>>
>>>"Mark T" <Mark_member@pathlink.com> wrote in message
>>>news:bvj7r4$30rl$1@digitaldaemon.com...
>>>
>>>
>>>>http://www.heron-language.com/c-sharp-critique.html
>>>
>>>It's an interesting read. I'd like to know what language the author
> 
> *does*
> 
>>>use, and why.
>>
>>Looks like he made his own: <http://www.heron-language.com/spec.html>
> 
> 
> I can understand his motivation to do that <g>.
> 


This seems interesting from heron:


|> Operator
The "|>" or pipe operator works as both an input and an output operator allowing data to be recieved from any source that implements the IWritePipe interface and to any source that implements the IReadPipe interface.

While I can see the motivation for an operator like that, I truly fail to see what's so different about it from the ordinary assignment operator.

They both implement "data <verb>s from point A to point B" where <verb> can be replaced by any number of words, such as move, flow, transfer.  I suppose if the language has weak (i.e. programmer-supported) notions of reference vs. value vs. abstracted contents, as evidenced by D's plethora of comparison operators, such a language may want to separate assignment of reference from assignment of value from assignment of contents, as well, but personally I'd rather unify, basically shield the programmer from having to worry about implementation details of the class types.

Unfortunately D doesn't allow you to overload assignment.

Sean

Vathix wrote:
| This seems interesting from heron:
|
|
||| Operator
| The "|>" or pipe operator works as both an input and an output
| operator allowing data to be recieved from any source that implements
| the IWritePipe interface and to any source that implements the
| IReadPipe interface.

"Sean L. Palmer" <palmer.sean@verizon.net> wrote in message news:bvjrpf$10ne$1@digitaldaemon.com...
> Unfortunately D doesn't allow you to overload assignment.

I have a strong negative view of the value of overloading assignment. By not overloading it, the semantics of it are reliable and repeatable. (For example, does it do a deep, shallow, or reference copy?)

"Walter" <walter@digitalmars.com> wrote in message news:bvjjso$j6h$1@digitaldaemon.com...
>
> "Mark T" <Mark_member@pathlink.com> wrote in message news:bvj7r4$30rl$1@digitaldaemon.com...
> > http://www.heron-language.com/c-sharp-critique.html
>
> It's an interesting read. I'd like to know what language the author *does* use, and why.

Thanks for the compliment on the article. As a couple of other have pointed out, I am working on my own language Heron. Here is what particularly motivates me about Heron :

- no class inheritance, polymorphism based entirely on interfaces and
delegation of implementation
- memory protection without garbage collection
- clear delineation between referencing variables and assigning values
- inexpensive templates (no code bloat)
- modular organization of code
- objects are value types that can be referenced if desired
- operator overloading
- no special array type, array is just a class defined in the standard
library as is every other primitive
- restricted run time type information through variants

I hope this helps answer your question Walter.

-- 
Christopher Diggins
yet another language designer
http://www.heron-language.com