Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple IPs #4

Open
aaronryank opened this issue Jun 24, 2017 · 5 comments
Open

Multiple IPs #4

aaronryank opened this issue Jun 24, 2017 · 5 comments

Comments

@aaronryank
Copy link
Owner

I plan on making Forked have multiple IPs. Is this a good idea?

@aaronryank
Copy link
Owner Author

Multiple-IP commands:

  • Commands to create IP at current point, beginning
  • Commands to jump to previous IP, next IP, 0-indexed IP, Top of stack representing an IP index

@catb0t
Copy link

catb0t commented Jun 25, 2017

This sounds cool. What when they cross paths? They just continue? Bounce off one another, or jump to a certain location given the stack value? Perhaps set your printer on fire?

@aaronryank
Copy link
Owner Author

aaronryank commented Jun 25, 2017

@catb0t I was planning on having the multiple IPs run asynchronously. i.e. only one going at a time.

However, this is why I put the spec on GitHub before implementing it - so I can get this kind of feedback. Do you think the IPs should be running synchronously, or should I wait to implement that in Fred (Forked/Thread, where : performs the system call fork())?

@catb0t
Copy link

catb0t commented Jul 18, 2017

Yeah, maybe synchronous IPs make the most sense in Fred. By which mechanism will a given IP be switched to?

@aaronryank
Copy link
Owner Author

aaronryank commented Jul 19, 2017

@catb0t define "mechanism". Do you mean the command? Or internal code/functions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants