Hi,
A while ago there were some blog posts made about using live coding
with PyGame which used the approach of continually reloading a
give module:
http://disruption.ca/archives/live-coding-games-in-python/
http://disruption.ca/archives/live-coding-continued/
Since a friend and I had written th
On 12/19/06, Greg Ewing <[EMAIL PROTECTED]> wrote:
Richard Tew wrote:
>> while True:
>> pass
>>
>> def fib(n):
>> return fib(n-1) + fib(n-2)
>> fib(100)
>
> If you were using Stackless Python, this sort of thing could
> easily be d
On 12/19/06, robomancer <[EMAIL PROTECTED]> wrote:
On the other hand, allowing people to run arbitrary code on your
machine is a Bad Idea even if you *can* ensure that the filesystem
isn't touched. What if they send any of the following?
while True:
pass
def fib(n):
return fib(n-1) + fib(n
On 12/4/06, Kamilche <[EMAIL PROTECTED]> wrote:
Kris Schnee wrote:
> So, as a lone developer, is it even worth trying to do this 3D system?
Truthfully, I wouldn't even attempt to write a 3D system from scratch.
There are lots of open source and commercial 3D engines out there - I'd
pick one and
On 8/10/06, Richard Tew <[EMAIL PROTECTED]> wrote:
On 8/9/06, Kris Schnee <[EMAIL PROTECTED]> wrote:
> Have a look at:
> http://produkkt.abraxas-medien.de/kkrieger
>
> This group used procedural synthesis to build a working FPS in < 96
> kilobytes. Repeat,
On 8/9/06, Kris Schnee <[EMAIL PROTECTED]> wrote:
Have a look at:
http://produkkt.abraxas-medien.de/kkrieger
This group used procedural synthesis to build a working FPS in < 96
kilobytes. Repeat, 96 kilobytes. They've also got graphical demos
weighing in at about 64KB. I'd like to know how it's
