search for: aquaconsol

.../R.framework/Resources/bin/R.bin Version: 1.9.0 (R 1.9.0) PID: 358 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000005 Thread 0 Crashed: 0 libSystem.B.dylib 0x90006e70 strlen + 0x50 1 R_aqua.so 0x0048699c HistFwd + 0x134 (aquaconsole.c:3451) 2 R_aqua.so 0x004825c8 KeybHandler + 0xd4 (aquaconsole.c:1370) 3 com.apple.HIToolbox 0x927d2330 DispatchEventToHandlers + 0x150 4 com.apple.HIToolbox 0x927d25a4 SendEventToEventTargetInternal + 0x174 5 com.apple.HIToolbox 0x927d6a0c SendEventToEventTargetWithOptions +...

Small things, mostly. 1. Buildproblem. Well-known and annoying. Build fails if debugging is on (which is the default) because Debugging.h breaks devQuartz.c compiles. If debugging is switched off on the command line or in the environment, then devQuartz.c builds, but aquaconsole.c does not compile, because it needs Debugging.h. I do not want to edit Apple system files, and not files in the R distribution either. 2. It would be useful if quartz devices could be opened from a menu. 3. Maybe a primary prompt in the input window would be useful. 4. Input and output windows...

..._FRAMEWORK_PATH, so we cannot use that elegant solution :( 4) warnings - aqua module under construction? I guess the aqua code is currently under construction, because it's probably compiled-in twice (in the libR and in aqua.so): [...] ld: warning multiple definitions of symbol _InitAquaIO aquaconsole.lo definition of _InitAquaIO in section (__TEXT,__text) /Work/R-builds/osx/r-devel/bin/R.framework/R(aqua.lo) definition of _InitAquaIO [...many warnings of the same kind follow...] I didn't invesitgate this further - if this is not intentional then I could have a look ... I suspect that...