|There's more than one way to do things|
Re^20: aXML doesn't compileby chromatic (Archbishop)
|on Nov 03, 2011 at 21:20 UTC||Need Help??|
But as for sharing it openly, all I get for being so kind is abuse...
Untrue. I'm not the only person to have gone out of my way to try to help you build something better.
Certainly you've received more abuse than anyone deserves, and that's not okay, but you also bear some responsibility for returning abuse in kind.
Even so, you've been arguing tooth and nail against the best advice available from some people who really know how parsers and compilers and grammars work—people who've studied and built such things that millions of people use directly and indirectly. This isn't because anyone wants to see you fail, but that you're bumping up against the limits of what is and isn't computable.
I believe (and I believe ikegami agrees) that your system requires anything which produces output to have an intimate knowledge of the compiling environment, plugins and all. If that's correct--even in a limited case--then you're especially vulnerable to attacks from untrusted user input from everything from denials of service to code injection and cross-site scripting. If you want to build a system that's truly robust and suitable for the general purposes which you've mentioned before, you'd do very well to stop and listen and consider our concerns.
Feel free to ignore anyone who tells you not to build aXML. If it's a good tool and it makes you more productive, great! Yet do consider that some of us have a lot of experience doing similar things, and we've run into these problems before, many times.
Improve your skills with Modern Perl: the free book.