Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Challenges

Comments on Write a Deadfish Interpreter

Parent

Write a Deadfish Interpreter

+6
−0

A rewrite of this SE question with a simpler input format and guidelines.

Challenge

Deadfish uses a single accumulator, on which all commands are to be performed.

It has the following commands:

Command Description
i increment the accumulator
d decrement the accumulator
s square the value of the accumulator
o output the value of the accumulator as a number

If, after executing a command, the accumulator is equal to -1 or equal to 256, the accumulator must be reset to zero.

I/O

Input can be taken as a single string, list of codepoints, or any other reasonable format. It is guaranteed that the input will only consist of deadfish commands.

Output can be given as an array of numbers, or just the numbers printed with separators between them.

Testcases

(some are borrowed from the Esolangs wiki)

iissso -> 0
diissisdo -> 288
iissisdddddddddddddddddddddddddddddddddo -> 0
isssoisoisoisoiso -> 1,4,25,676,458329
ooooosioiiisooo -> 0,0,0,0,0,1,16,16,16
iiii -> nothing
iiiiiiiissdiiiiiiiiiiiiiiiiio -> 4112
o -> 0
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+2
−0

Lua 5.4.4, 99 bytes

_=0s:gsub('.',function(c)_=({d=_-1,i=_+1;s=_*_})[c]or print(_)or _ _=({[256]=0,[-1]=0})[_]or _ end)

Try it online!

Thanks to @orthoplex for more shortening.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

Tables to the rescue ^^ ```lua _=0 for c in s:gmatch'.'do _=({d=_-1,i=_+1;s=_*_})[c]or print(_)or... (4 comments)
Tables to the rescue ^^ ```lua _=0 for c in s:gmatch'.'do _=({d=_-1,i=_+1;s=_*_})[c]or print(_)or...
orthoplex‭ wrote over 2 years ago

Tables to the rescue ^^

_=0
for c in s:gmatch'.'do
_=({d=_-1,i=_+1;s=_*_})[c]or print(_)or _
_=({[256]=0,[-1]=0})[_]or _
end
orthoplex‭ wrote over 2 years ago

At first, I thought you were cheesing the test cases, but you're right, -1 is the only negative number you can possibly get. Clever! The penultimate line should then be

_=(_==256or _<0)and 0or _
Zakk‭ wrote over 2 years ago · edited over 2 years ago

_=(_==256or _<0)and 0or _

You are right.

Tables to the rescue ^^

Man! That's just brilliant! Again, thanks for pointing this out.

Btw, I am really curious about how much experience you have with Lua.

Zakk‭ wrote over 2 years ago

Though both of s:gsub and for..in versions are equal in length, the former can be one byte shorter, because sticking an s to 0 doesn't make the Lua interpreter unhappy, contrary to sticking an f to 0.

_=0s:gsub('.',function(c)_=({d=_-1,i=_+1;s=_*_})[c]or print(_)or _ _=({[256]=0,[-1]=0})[_]or _ end)