« first day    last day (29 days later) » 

12:08 AM
maybe i'll add if as well
the if structure (...) being equivalent to [...(store value in variable that won't otherwise be used)(value is now zero)](get the value back)
should only require one more temp variable
 
 
1 hour later…
1:24 AM
not really sure if i will call it real...
 
1:37 AM
uh... I'll call it Strider I guess
actually i don't think i'll commit to a name yet
 
1:51 AM
Undefined?
 
undefined seems like...
naming something after the fact it doesn't have a name doesn't seem ideal to me
like "haha meta i called the language unnamed-language" doesn't seem very clever to me as it tries to be
how about
quarterstaff
what with it being minimal
 
Call it Lemon... why not. Have LemonA, LemonB, LemonC, ...
 
what do you mean by lemonA
I think i actually like the name quarterstaff
i/o in integers or ascii?
maybe i'm adding too many miscellaneous functions...
i'm also going to need to make an interpreter for the specific bf cell size and behaviour and stuff
 
2:39 AM
ok did i forget something?
[] loop
{} inverted loop
() if
<> inverted if
~  assign to following variable. value = 0
-  invert current value
.  value = 0
=  value = sign(value)
*  multiply value by 2
/  integer divide value by 2, rounding down
%  value is now value modulo 2
?  input - works like the underlying bf implementation. inputs ord(character) into value
!  output- works like the underlying bf implementation. outputs chr(value)
[string of alphabetics] variable. when not preceded by ~, add variable to current value
[string of numerics] add the number to the value
inverted means instead of if(value) it's if(not value)
 
Looks sensible.
 
thanks
i could minimalise it though
[] loop
~  assign to following variable. value = 0
-  invert current value
?  input - works like the underlying bf implementation. inputs ord(character) into value
!  output- works like the underlying bf implementation. outputs chr(value)
[string of alphabetics] variable. when not preceded by ~, add variable to current value
[string of numerics] add the number to the value
[any character not used somewhere here] separator
minimalised
i'm conflicted...
anyway, maybe i should work on the bf implementation
 
 
1 hour later…
4:03 AM
"done"
most of the work was done by me in the past
should i make a compiler or an interpreter for the language prior to the challenge?
 
That would be incredibly useful for submission validation
 
it's more the question of which though
it's kind of annoying that the idiomatic way to ask that has a literal meaning different to the intended meaning
which of a compiler and an interpreter should i make
 
@DestructibleLemon Whichever is less effort?
 
it's more that i like the idea of only having compilers for the language?
 
Once again the comma helps: Should I make a compiler, or an interpreter, before the challenge?
 
4:10 AM
but yeah, i guess i'll just interpret it
@Οurous not really sure about that but ok
 
@DestructibleLemon When in doubt add more commas. Should I make a compiler, or, an interpreter, before the challenge?
 
should, i, make, a compiler, or, an interpreter, before, the challenge,?
 
Yes
(an interpreter, seems like less work.)
 
seems, like, less work
also apparently the interpreter already stripped ? when that was supposed to be a command wow wacky
yeah, i think the interpreter will also look pretty similar to the bf interpreter
I still can't totally decide if i like minimalist or more features for this challenge
idea: program in implicit loop, with if commands and halt command
nah not very nice
 
4:40 AM
what should the behaviour of assign be if there's nothing next to it? error?
 
Parse error.
 
 
6 hours later…
10:56 AM
72!108~a101!a!a!3a!44!32!87!a3!a6!a!100!33!10!
hello world
truth machine: 49-?{49!}49!
48~a?-a[2a!1-]a!
49-?{49!}49!
ok that wasn't an optimisation
room topic changed to Quarterstaff to bf challenge: The interpreters have been made, so the challenge will be made soon (no tags)
room topic changed to Quarterstaff to BF challenge: The interpreters have been made, so the challenge will be made soon (no tags)
 

« first day    last day (29 days later) »