Open GoogleCodeExporter opened 9 years ago
thanks for the suggestion. I fully agree this would be a nice thing to have..
though it seemed more important before 0.6, because I wasn't sure scalability
would be good enough without it. perhaps if there's this 10,000 line program
that I cannot get shedskin to analyze within a reasonable amount of time, I
will look into it again.. the largest current example program (c64 emulator)
compiles in a few minutes, probably within one minute with some minor
improvements and a fast CPU in a few years..
a related approach would be to just profile a program, and store type
information for use in inference or code generation. that would also make it
faster to analyze a large program for the first time, so I think this is a
better approach. in the newsgroup I posted a simple example that shows a useful
profiler can probably be written in a few hundred lines of code. it would be
very nice to have an independent project that allows to store this information
in some standard format, for use in any python implementation (if there isn't
one already). perhaps shedskin could then also output to this format. it's
probalby not something I will work on myself though.
Original comment by mark.duf...@gmail.com
on 15 Dec 2010 at 9:41
Issue 134 has been merged into this issue.
Original comment by mark.duf...@gmail.com
on 16 Jul 2011 at 9:54
Original comment by mark.duf...@gmail.com
on 16 Jul 2011 at 9:55
Original issue reported on code.google.com by
fahh...@gmail.com
on 15 Dec 2010 at 3:30