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

A parameter to set "stricted mode Pico-8" #51

Closed
mdtrooper opened this issue Apr 18, 2016 · 7 comments
Closed

A parameter to set "stricted mode Pico-8" #51

mdtrooper opened this issue Apr 18, 2016 · 7 comments

Comments

@mdtrooper
Copy link

Hi.

I think that is good to set a parameter to set "stricted mode Pico-8"

Thanks.

@Shoozza
Copy link
Member

Shoozza commented Aug 4, 2016

How would that mode differ from the current implementation?

@mdtrooper
Copy link
Author

This is a good question. Well, the picolove with the strict param set runs with the limitations (memory and others...) of pico-8.

@vanfanel
Copy link

@mdtrooper : from what I understand, it seems these limitations are arbitrary, so what would "strict pico-8 mode" bring? Maybe rejecting to run non-strict pico-8 games if their resource requeriments are above those of the original, closed pico-8 implementation?
Maybe not using them (if you don't want) would be enough in that case...

@Shoozza
Copy link
Member

Shoozza commented Feb 20, 2019

If we want to add this, we'd need to collect all limitations first.
Note that limitations change between pico-8 versions.

If someone can list all the limitations that would be a start.

@gamax92
Copy link
Contributor

gamax92 commented Feb 21, 2019

Implementing a memory limiter isn't really possible when your implementation of a Lua based product is in Lua itself.
CPU limits is somewhat possible but the whole picolove is writtein in Lua also makes this not fully accurate
picolove would need to be rewritten to not use any string metatable to restrict pico-8 code from accessing the string metatable too

(Also hi, sorry I've been away for a long time)

@Shoozza
Copy link
Member

Shoozza commented Apr 22, 2019

Ah I see - Thanks for the clarifications.
I don't think I'd want to rewrite picolove to support these limitations.
(Welcome back!)

@Shoozza
Copy link
Member

Shoozza commented May 2, 2019

Wontfix see comment above

@Shoozza Shoozza closed this as completed May 2, 2019
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

4 participants