Philip - if this is a one-time deal, I would agree with the consensus: write out the data as an ASCII file that you'll be able to parse easily in J. Something like
Name=prices/size=10 252/type=N 1.1526116 1.4987268 1.2532713 1.3476891 1.8013837 1.9734297 2.2062007 2.3142009 2.488164... for each variable should be easy enough to generate in APL and parse into J. If you need to do this regularly, I worked out a scheme for transferring data between Dyalog APL and J by writing some Dyalog functions to read and write arrays in the J internal format. This is detailed in my paper presented at APL2002: *J and Dyalog APL Sharing Resources: Can't We All Just Get Along? *It's available at http://portal.acm.org/ft_gateway.cfm?id=602247&type=pdf&dl=GUIDE&dl=ACM if you are an ACM member. You can contact me privately if you're interested in pursuing this avenue. If you pursue the ASCII method, the one thing I can think of to be aware of is that APLPlus may support heterogeneous arrays which have to be boxed in J. Good luck, Devon On 5/30/07, Philip A. Viton <[EMAIL PROTECTED]> wrote:
Can anyone suggest a simple strategy for converting a bunch of APL-PLUS/win component (.sf) to J's equivalent jfiles? All the data in the sf files are rank-1 or 2 non-nested objects. The only thing I can think of is to put each componenet of the sf file into a text file, and then read it into J. Are there better solutions? In particular, could one make the workspace-interchange-file format work with J? ------------------------ Philip A. Viton City Planning, Ohio State University 275 West Woodruff Avenue, Columbus OH 43210 [EMAIL PROTECTED] ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
-- Devon McCormick, CFA ^me^ at acm. org is my preferred e-mail ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
