You can even enhance it to whatever extent you want, by adding extra type-in windows, menus, buttons and whatever the application might need.
The best thing about it for your requirements is that the data being edited never needs to go outside your perl process.
Meanwhile, trying to use emacs this way seems like a non-starter relatively more complicated and difficult. Emacs needs to open a data file, and load it into a buffer, in order to edit text data. If you have figured out a way to have emacs run as an interactive process using stdin and stdout (not a disk file) as the source and destination of text data for an editing buffer, I'd be curious to hear how you do that, because I've never seen it done (in over 15 years of using emacs).
update: Having just seen educated_foo's reply, that looks like a good approach, assuming there really are things in emacs that make it especially good for the task at hand. One thing that wasn't mentioned there (in case you're not familiar with emacsclient) is that you need a separate instance of emacs already running, and that instance needs to execute the "server-start" elisp command. It will then sit idle until an emacsclient process runs to give it something to do.
In reply to Re: In memory edit of perl data with emacs
by graff
in thread In memory edit of perl data with emacs
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |