On Mon, Jul 8, 2013 at 7:24 AM, David Beazley <[email protected]> wrote: > So, I was thinking about the PLY parsetab.py file this morning. What would > people think if the data contained in this file was simply written somewhere > in the system temporary directory (e.g., /tmp) and regenerated as needed? > Under such a scheme, everything would work pretty much the way it does now > except that I could deprecate that whole sea of options about parsetab files, > output directories, and whatnot. The only real downside that I can think of > is that the parser tables would have to be regenerated after a reboot. > However, who would really care given that it only takes a few seconds? > > Thoughts?
Can you provide more information about how this would work? Say user1 has a tool installed, built on PLY, that's using version 1.0 of the grammar, and user2 has the same tool installed, but it's using version 2.0 of the grammar. Do they both get written to the same file when the parse tables are generated? Would the developer using PLY provide something that's used to influence how the directory or file gets named? Is there an issue with someone monkeying with parse tables to make something happen that shouldn't happen--a security problem of sorts? Could we still package the parsetab.py file with our RPM install, if we wanted to avoid the overhead? Sorry for the dumb questions! -John -- You received this message because you are subscribed to the Google Groups "ply-hack" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ply-hack/CAEBDL5XX0Cj54DPktUsjVJRqjBiivNUL4Jtx_3k2jzdmxBVRtQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
