Re^4: Is this proof of concept too evil?

I think I will stick with tie for now:

Performance is not an issue in this case
Both of those are modules that use c/c++ and are not core
I am keeping my deps at a minimum when possible because my module will bundle itself for other systems, the less I have to bundle the better, currently it is YAML::Syck and Getopt::Long only.
This is a proof of concept, the class I am tying to in production does more

Comment on Re^4: Is this proof of concept too evil?

Replies are listed 'Best First'.
Re^5: Is this proof of concept too evil? by ikegami (Patriarch) on Jan 18, 2009 at 02:23 UTC
Both of those are modules that use c/c++ and are not core That's a non-issue. Lexical::Alias is trivial to build using `cpan` and available via `ppm` for Windows.	[reply] [d/l] [select]
Re^6: Is this proof of concept too evil? by exodist (Monk) on Jan 18, 2009 at 07:31 UTC
Sorry, it must have sounded like I did not want to use it just because of that.. non-core and c/c++ modules are not a problem, however they would break some parts of what I am working on.	[reply]