Talk:~-~!

File suffix
Sounds like you've got a good language going! May I recommend a change of the file extension? Since Esoteric programming languages are many times posted on servers, kept in logs, and generally stored, kind of like art. But just like art, an odd frame (Or extension in this case) can cause files or art not to be stored. If you want your files to be kept on storage servers, logged away historically, it may be hard for admins to keep files when they have an extension larger than 3 characters. The main problem is that in common storage systems like flash drives, CDs, and so on, there is only space for three characters in the extension. Of course, it's just a recommendation, but it might be a good idea, maybe ".noc" or ".tdt" for tilde dash tilde. Nathanator1416j (talk) 23:18, 6 February 2014 (UTC)

Getting odd numbers back after ~= (let 1 = 2)
I can think of at least two ways to get the number one, and therefore odd numbers in general, back:


 * ~= or for the uninitiated, let ~ (1) equal 2
 * 1) ~=<~/~> or for the uninitiated, let ~ (1=2) equal 2/2
 * 2) ~=<~==~> or for the uninitiated, let ~ (1=2) equal 2==2

Changing the operator and variable symbols, however, is a good way to lose them forever.

Dropping the requirement of bignums
Instead of demanding the implementation to store the program's data in arbitrary-precision bignums, how about just having each number in a fixed sized signed integer? The inplementation could store the data in 64 / 128 bit integers (which, if you do the math, can hold 16 characters of a string in ~-~!), for instance, and then provide a symbol that indicates the maximum storage size for a number, say ? It would return the amount of useable bits for a number. I'm only asking because I plan to write an implementation for this esolang, but I'll be doing it in an environment where I can't exactly have direct access to the heap to provide bignums. Xav737 (talk) 18:32, 1 August 2017 (UTC)