J
jquerijero
Guest
[quote user="dbeavon"] Yes, this is fine. R-code is not platform dependent. See KB for full explanation: "6: R-code is NOT platform dependent" here: Progress KB - Do I Need to Recompile .r Code When Porting/Deploying an Application ? (As a side, we also compile on Windows and ship the R-code to HP-UX-IA64. Those are about as different as two platforms can be. Thank goodness that HP-UX won't be a consideration very much longer...) Insofar as running platform-specific code, you just check the result of OPSYS and do a different thing if you are on a non-windows platform. (Oddly the identifier for windows is "WIN32" even if your stuff is all 64 bit.) ? 1 2 3 4 5 CASE OPSYS : WHEN "unix" THEN OS-COMMAND ls. WHEN "win32" THEN OS-COMMAND dir . OTHERWISE MESSAGE OPSYS "is an unsupported operating system" . END CASE . I'd highly recommend reading this documentation if you do development that targets multiple platforms. "Coding for Portability" here: OpenEdge 11.7 Product Documentation - Wiki - OpenEdge General - Progress Community Hope this helps, David [/quote] Thanks. What's really throwing me off are the Windows specific variable definitions (ex. AS System.Object). I'm not sure if those are seen early on by the platform the r-code is running on, or only when the variable is finally hit/run during run-time.
Continue reading...
Continue reading...