@AquaTart: What do you think about dropping Python-style indexing, x[2:5], and using x[2..5] instead?

Well, x[2..5) to match what Python would give.

What about the plans we had previously for slicing?

Previous plans were Python-style.

Right, but we had some more exotic ideas.

Here, lemme dig them up

But if I'm going to make x[2,5] and x[2,5,*[7..10]] possible, then why not just drop x[2:5] and go with x[2..5)?

I suppose.

^ That's what I was looking for

Yeah, and I still want to make that possible.

But think, why couldn't we do that with ranges in general?

[2..20:2;3]

please include braces in this language :3

Or a braces mode.

There are already braces.

\o/

range_start..range_end is from Perl, right?

Suggestion: make {<item> : <conds>} also set-builder, if possible :D I love that notation

@MarsUltor huhwat?

@MarsUltor Ruby, actually.

gets stuff mixed up

@CᴏɴᴏʀO'Bʀɪᴇɴ Set builders are already planned. See the syntax spec in the sidebar.

Haven't used Perl/Ruby/Lisp at all yet

For what it's worth, neither have I. :P

@El'endiaStarman I'm reading it atm :D I was wondering if you could include an alternate syntax. ^_^

Me neither @mars

@CᴏɴᴏʀO'Bʀɪᴇɴ Wait what you can do that?

AquaTart has used Perl and Ruby, and I've been reading essays by a guy that loves Lisp.

Oh

@MarsUltor Do what?

Inline ping?

I've seen some Ruby (mainly golfscript source)

@Cᴏɴᴏʀ Test

hi!

@CᴏɴᴏʀO'Bʀɪᴇɴ I'm not terribly against the idea of multiple syntaxes for the same thing, but it's probably better to avoid.

Um.

did that ping?

@El'endiaStarman Just wondering ^_^ and just a suggestion

@MarsUltor Yup!

@C test

@MarsUltor At least 3 letters

Oh

> <: - a <: <expr> means that a, wherever used, has the value of the expression at that time.

Does that mean it's a constant, or what?

Nope.

What is it, then? :/

a = lambda m: foo

I think

ohhhh

nope

cool!

darn

XD

@El'endiaStarman What does it do?

I'm typing that out...

lel

> User-defined functions can be defined to be infix.

I am now a devoted follower

Let's say I have a function that draws Beziér curves given a series of coordinate pairs, which are set interactively by dragging circles around. Instead of updating this list of coordinate pairs based on the circle locations "by hand", by coding it in an update loop, I can use the <: operator to "link" circle locations with input coordinates, thus obviating the need to write the code myself.

Oh

This will not necessarily be more efficient internally, but it will probably be more programmer efficient.

So a = new Func(args=>body);

args.OnChanged += new Func(value_of_a => a())

^ SOmething like that?

....maybe?

Uh, lemme type a little code sample.

What language is that? Pseudo code?

Basically it means you have a hook into each of the properties passed in and update a as they're changed?

> x = 5
5
> y <: 3*x
15
> x = 7
7
> y
21

@CᴏɴᴏʀO'Bʀɪᴇɴ Really badly written C#

@El'endiaStarman ^^^?

@El'endiaStarman Do you have an interpreter already?

Or is that just explanation

@CᴏɴᴏʀO'Bʀɪᴇɴ Working on one.

And no, don't have a REPL yet.

Other than my brain. :P

@CᴏɴᴏʀO'Bʀɪᴇɴ They're mostly working on parsing I think.

Yep.

Github?

@CᴏɴᴏʀO'Bʀɪᴇɴ cloud9

Link?

@MarsUltor I'm planning on implementing it such that when a is accessed, then it evaluates the linked expression.

@CᴏɴᴏʀO'Bʀɪᴇɴ They're gonna sync it with github soon™

6-8 weeks :P

:P

@CᴏɴᴏʀO'Bʀɪᴇɴ ide.c9.io/elendiastarman/pytek

November 1st, then?

@El'endiaStarman Then basically a = lambda args: body

@El'endiaStarman opens bookmarks

then when you use a it actually does a()?

@MarsUltor But it behaves like an integer (in the case I typed above).

@MarsUltor Yes, I think you're understanding right.

Yeah, but a() will return the correct type anyway

yeah

This was the linking thing you were talking about in The Nineteenth Byte, right?

Main?

I have no idea what I'm saying

Main chat?

heh heh

oh lol I'm late

Well, I still don't know what you're talking about. Quote/permalink?

Pretty sure you asked if there was a way to link both ways

Or something

Oh yeah, the idea was raised.

Someone else said that "link" suggests to them that it's bidirectional.

As in, change y and x will change.

That's still possible

Just not very important

Yes.

But

If/when I implement that, it will only work under some conditions.

You need a way to initialise circular-linked variables

as in when b = function(a) and a = function(b)

Yep, planning on figuring that out.

I think you should have internal values, the functions actually act on the internal values, and assigning to them assigns to internal values if types match

We'll see.

So

What are you working on right now?

I'm not sure what you mean.

1) Did you turn into Marky? 2) What will happen when you implement compilation?

I don't plan on implementing compilation.

Wait

It's written in Python, right?

yes

Are you going to make an interpreter with PyPy?

We looked into that and it looks like PyPy's translation toolchain doesn't support Python 3.

I've told AquaTart that I don't mind if he converts the Python 3 code to Python 2, and then uses PyPy.

I think using PyPy would be good, if only for the speed

Yes. That is not a concern at present though.

I care about programmer speed at the moment, not computer speed.

If speed was the most important thing, we'd all be using C.

But there's not much point if it runs too slowly

Oh, but there is!

Computers are getting faster all the time.

And programmers will like to program in languages that are fast to code.

@El'endiaStarman I know.

@El'endiaStarman But for things like electrons in a wire, the fastest Pytek version may be considerably slower than orlp's PyPy version

@MarsUltor Aaaaand orlp used C.

Speed mattered there.

Most of the time, it doesn't.

I guess

Premature optimization is a baaad thing.

@El'endiaStarman Why?

Priority #1 is making it work like it should.

Caring about speed at the outset is putting the cart before the horse.

Well, I think eventually the main interpreter should use PyPy eventually.

Sure, I'm not disputing that.

I wonder if there will be native unit support

Unit?

As in mm/m/ft/yd etc

mostly conversion support.

Something like this.

Oh, yeah, I'll add those to the to-do list.

I'll probably make that an import though.

Will you (eventually) have syntax editable by imports? (like Python's __future__ statements)

I'd like to.

:D

Try/except? Nah, try/fail.

Alright, went through the transcript and put most of the ideas in a Google Doc: Pytek Mishmash.

It is, obviously, not done, but it's a good start!

@El'endiaStarman Do you mind if try starting the docs (on a GitHub repo, and using the stuff from the pastebin?)

@MarsUltor I'll handle that myself.

With ReadTheDocs?

I've looked at that. Still not sure if I'll use them.

@El'endiaStarman Well, I would prefer having docs on a site specialized for documentation (GitHub wiki/Builtin GitHub markdown viewer is okay though)

@El'endiaStarman I think there should be a non-file-object read() and write() method that opens, reads/writes, and closes a file.

@MarsUltor \slurp and \put do that. It's all in my RL secret notebook of aecret STDLIB things

*secret

Oh wow, El'endia made a large nonsecret document of nonsecret STDLIB things.

...and he got most of the things I had in my sercret notebook

@El'endiaStarman On *nix systems, do you think modules should go in /usr/lib/pytek/...?

I have some of the code for the preprocessor up but I don't think it'll handle escaped quotes properly

Parsing this is hard