← Thread:Talk:Multithreading/Reinventing wheels?/reply (2)
I'd be in favour of disabling multi-threading in the rumble, or somehow only allowing a single thread to run at the same time. Otherwise there could be some very dirty tactics like starving the opponent of CPU or memory bandwidth during their turns, which is against the spirit of trying to keep the bots' processing isolated except through the robocode engine.
You do not have permission to edit this page, for the following reasons:
- The action you have requested is limited to users in the group: Users.
- You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.
You can view and copy the source of this page.Xor (talk)
I usually put the engine in debug mode if I am going to be logging a lot of data. Also, robocode does increase your processing time allowed if you do any file IO.
But debug mode disables security iirc? Then this mode is unsafe for running with arbitrary opponent. Also it seems that skipped turns has no special handling if you do IO. It just increases the max skipped turns allowed before you get disabled
Java already has nonblocking IO support, may be we should support this in robocode as well. Currently doing so requires disabling security.