ooc-dev team mailing list archive

[Amos Wenger <amoswenger@xxxxxxxxx>]

In fact, your remark makes me realize that, in fact, the backslash syntax is
sometimes confusing/ambiguous. Moreover, I'd like to make it more flexible.

Before ooc, I had a programming language project called "Hackit", which was
tube-based (some would say stream-oriented now). A tube could be opened,
closed, receive and yield data, and that'd allow parallel processing, etc.

I have abandoned the Hackit compiler I had written, but I think some of
these features
could be integrated into ooc.

I'll think more about this backslash syntax and how to generalize it (e.g.
how to
control ordering, parallel tasks, permutations, sorting, etc.)

Sorry for the half-backed draft, more to follow soon.

Amos

2009/7/2 Justin Poliey <jdp34@xxxxxxxx>

> Yeah that is pretty exciting. So about the backslashes, the only
> example that I wasn't quite sure about was the printf("%d, ", \(1, 2,
> 3)) one. Would it be the same as calling \(1, 2, 3).printf("%d, ")?
> Just a different way of doing the same operation as the \l.printInfo()
> example? Anyway, I think that's a powerful construct to have.
>
> Justin
>
> On Wed, Jul 1, 2009 at 10:55 AM, Amos Wenger<amoswenger@xxxxxxxxx> wrote:
> > I've tried to explicit what the backslash is all about, see
> > http://ooc-lang.org/draft
> >
> > About Steve Dekorte: I've had a lengthy discussion with him on #ooc-lang
> > about ooc.
> > He said that ooc looked good, that he wanted to do his own low level
> > language for
> > a long time, and that it was the closest to what he had in mind.
> > So he seemed very interested and he plans to hack on it. (He's
> particularly
> > interested
> > in full jit suport).
> > I didn't want to tell you yet so you didn't have false hopes, but now
> that
> > he's blogged it, well... =)
> >
> >
> > 2009/7/1 Justin Poliey <jdp34@xxxxxxxx>
> >>
> >> Great work, I'm looking forward to the closures support. What's the
> >> backslash syntax all about? I've never really seen anything like that
> >> before. Also, on a slightly unrelated note:
> >> http://www.dekorte.com/blog/blog.cgi?do=item&id=4077 Steve Dekorte
> >> (creator of the Io language) has covered OOC, which is pretty awesome.
> >>
> >> Justin
> >>
> >> On Tue, Jun 30, 2009 at 6:10 PM, Amos Wenger<amoswenger@xxxxxxxxx>
> wrote:
> >> > Hi all,
> >> >
> >> > I am so sleep deprived right now that I will probably fall in the next
> >> > minutes, but I had so ideas I wanted written down.
> >> > I have created this page on ooc-lang so you all can see my vision of
> >> > ooc's
> >> > syntaxic future:
> >> >
> >> > http://ooc-lang.org/draft
> >> >
> >> > Enjoy,
> >> >
> >> > Amos
> >> >
> >> > _______________________________________________
> >> > Mailing list: https://launchpad.net/~ooc-dev<https://launchpad.net/%7Eooc-dev>
> >> > Post to     : ooc-dev@xxxxxxxxxxxxxxxxxxx
> >> > Unsubscribe : https://launchpad.net/~ooc-dev<https://launchpad.net/%7Eooc-dev>
> >> > More help   : https://help.launchpad.net/ListHelp
> >> >
> >> >
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~ooc-dev<https://launchpad.net/%7Eooc-dev>
> > Post to     : ooc-dev@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~ooc-dev<https://launchpad.net/%7Eooc-dev>
> > More help   : https://help.launchpad.net/ListHelp
> >
> >
>