#624: pluggable everything
---------------------+------------------------------------------------------
Reporter: allison | Owner:
Type: roadmap | Status: new
Priority: normal | Milestone: 3.6
Component: none | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
---------------------+------------------------------------------------------
Comment(by Quevlar):
Hi,
The idea that I have about a plugin is that consist of two parts.
A group of files that are going to be transformed for a set of tools(like
a compiler).
A configuration script that have the parameters passed to this tools.
The script is something like
[plugin]
plugin_name = myplugin
plugin_dir = /home/miuser/myplugindir #or '/home/miuser/miplugin'
installed_plugin = /usr/local/application #is installed in
/usr/local/application/myplugin
[compiler]
compiler_name = gcc
install_root = installed_plugin
#output_extension =
#if output_extension is a comment uses the default extension
It can be parsed using regex
The apache configuration file uses something like namespaces or blocks
I think tests can be plugins
It's only one instruction
[script]
language_used = perl
All the languages can be made pluggins, and thinking in nanoparrot pasm
and pir can be handled like plugins too.
Sincerely,
Igor
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/624#comment:1>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
