#10

Yes, thatā€™s what I was thinking.

#11

Iā€™ve added it to the list at the top

2 Likes
#12

From a non-programmer, looks great! More room for stuff.

1 Like
#13

Just to play devilā€™s advocate - I remember speaking with @tehn about this way back when the language was being designed and it was a conscious decision not to use these.

The principle justification being that by using words it made people think less of the scripts as ā€˜equationsā€™ in the way one learns in school, and instead a ā€˜tt commandā€™. It was thought the prefix notation might be more difficult when using the same operators we know as applying to infix.

Perhaps the language is established enough now that we can live with it, or perhaps all of us need to think more about what itā€™s like for a brand new user to get on board. Obviously having them as aliases means the existing tutorials and info still applies, but Iā€™d bet most shared examples moving forward will use the aliases and thus could be potentially confusing.

Just some thoughts! Please disagree with me!

7 Likes
#14

+1
the use of words is one of main reasons i dove into TT

2 Likes
#15

The simplicity of the syntax initially drew me to the TT as well, but within a few hours of owning it, the line character limit frustrated the hell out of me. If scrolling or wrapped lines canā€™t be added then Iā€™m all for the short aliases.

#17

Excited for these simple, but thoughtful and useful tweaks!

#18

I definitely qualify as a non-coder new user of TT. For me, any change to the syntax that makes building a patch more efficient while retaining creative restraints and functional transparency (as in, I can understand what is happening and how to control it) is positive! In response to @Galapagoose, I think that as long as the tutorials teach and guide a new user to understand how everything works and then reveals the op aliases as a convenience, that would be easy enough to follow and a delightful treat at the end of rigorous learning. :icecream:

3 Likes
#19

i have no intention to update the tutorials.

ā€œwordsā€ will be standard, but these aliases would be great optimizations for those who want them.

3 Likes
#20

As a coder I would like some fork of TT firmware or possibility to enable these aliases, but arguments for not having them totally make sense also :cat:

#21

to clarify, and point out that this isnā€™t a big issue all around, both ADD and + would work interchangeably. no fork needed, no alternative firmware needed.

the only issue is that if someone shares a script here that has + in it and the uninitiated get confused.

#22

Progressā€¦

symbols.jpg800Ɨ461 71.4 KB

In case anyone is wondering:

X 0
L 0 3 : X + X << P I I

is a binary to decimal converter. And itā€™s just as complicated to get your head around without the symbolsā€¦

6 Likes
#23

Not sure how I missed this. Maybe Iā€™ve been stoned on solder paste fumes.

This is great. Iā€™ve been finding myself wanting a bit more room on each line. Having more compact versions of basic math functions helps!

Thanks again, @sam, for all that you are doing for the Teletype ecosystem. It really is spectacular.

1 Like
#24

The code to add the aliases is really simple (and adds little overhead), once itā€™s been merged, we can go through and add shortened versions of the TXi and TXo ops too.

I really need to get some sort of automated documentation system up and running for ops though!

3 Likes
#25

Hi there, is there a list of the aliases somewhere ?

#26

itā€™s listed in the docs separately for each op.

OP OP (set) Alias Description
ADD x y - + add x and y together

https://monome.org/docs/modular/teletype/manual/#maths

https://monome.org/docs/modular/teletype/manual/#alphabetical-list-of-ops-and-mods

1 Like
#27

Thanks. Iā€™ll compile them myself, then. For the purpose of memorizing, and work my skills.

2 Likes
#28

If you know Python, you could hack some of the scripts that generate the docs to list out the aliases. Otherwise the easiest option is probably to just go through the list.

#29

Post here if/when you do! I would find it useful.
And thank you in advance!

1 Like
#30

Thanks.
Iā€™ll publish it here as a rough copy/paste when itā€™s done (and if itā€™s done). I donā€™t have the skills to do much more.