Re: sqlite3 on macOS

tories > can > sometimes (!) be fixed by ./configure options. In the above case something > along the > lines of > > ./configure --with-sqlite3=/usr/local/opt > > may have worked (whether it does or does not work depends entirely on the m4 > macro). > > Best

Re: sqlite3 on macOS

ossible to use git (with > some minor > quirks due to the lack of SVN version numbers). > > Best Regards, > Jürgen > > > On 10/5/22 11:32 PM, Peter Teeson wrote: >> Hi Jürgen: >> >> My recollection is that Apple used to distribute a number of command

Re: sqlite3 on macOS

you have to install svn manually. Not sure about git > because I cant > remember if it was there initially or if I installed it later on. > > Best Regards, > Jürgen > > > On 10/8/22 9:50 PM, Peter Teeson wrote: >> Hi Jürgen: >> >> Sadly Apple’s favou

Re: Latin-American APL keyboard layout?

There is this marvellous utility that I have used. It might be helpful. https://software.sil.org/ukelele/ If the user is on an Apple Mac then this extract from the Installation Guide may be helpful. Keyboard Setup To make the keyboard work correctly with the

Re: Still some issues/warnings..

t repository* (which uses a different wbb server setup) then > neither firefox nor chromium renders the files properly. In both cases all > Doxygen files are present. > > Best regards, > Jürgen > > > On 10/18/22 8:03 PM, Peter Teeson wrote: >> Hi Jürgen: >> &g

Re: Still some issues/warnings..

configure: creating buildtag.hh... readlink: illegal option -- f > [-f format HYH > On Oct 18, 2022, at 4:04 PM, Peter Teeson wrote: > > STAT(1) BSD General Commands Manual STAT(1) > > NAME > readlink, stat -- display file

Re: Still some issues/warnings..

ms to be an issue with your makeinfo version (mine is 6.5 > and I am not getting these warnings), > Line 649 ff. and 741 ff. should be fixed (in m4/ax_lib_sqlite3.m4). > > SVN 1604. > > Best Regards, > Jürgen > > > On 10/18/22 8:03 PM, Peter Teeson wrote: >&

Re: Still some issues/warnings..

hope macOS has dirname, has it? > > Best Regards, > Jürgen > > > On 10/19/22 6:19 PM, Peter Teeson wrote: >> Hi Jürgen: >> >> So sorry but we’re not done yet…… respect Peter >> >> Gandalf:~ pteeson$ cd /Volumes/Data/GNUAPL-on-Mac-WS/GNUapl >>

Re: DALY SUBDIRS in makefile

What is your operating system? > On Oct 30, 2022, at 11:22 PM, Peri Didaskalou wrote: > > Hello, > > Today I tried configuring and making GNU APL both via github and subversion. > > Either way configure kept getting stuck on not finding the DALY subdirs under > /doc /wslib3 and /wslib5, at

Re: Compilation problem

FWIW I also get the same error on macOS - been trying for days to hunt down problem but so far no answer. Looking at the ./configure code but am boggled by it and struggling to zone in on the correct area, I work in Xcode so no idea what to use to dynamically debug/trace in Terminal Gandalf:tr

Re: Compilation problem

P.S to my previous post…. > Apple has officially deprecated Python 2.7 in macOS Monterey 12.3. The company is advising its developers to use an alter

Re: Compilation problem

Why not make a note in the python README for users to make a symbolic link from their actual python location to a standard place such as /usr/include/python? Then configure need only refer to that. > On May 25, 2023, at 5:34 AM, Dr. Jürgen Sauermann > wrote: > > actually: > > CXXFLAGS="-I

2 warnings and an error

Hi Jürgen:Full logs attached at bottom. kind regards PeterGandalf:~ pteeson$ cd /Volumes/Data/GNUAPL-on-Mac-WS/GNUapl Gandalf:GNUapl pteeson$  svn co http://svn.savannah.gnu.org/svn/apl/trunk > svn-log 2>&1A    trunk/m4…..A    trunk/aclocal.m4Checked out revision 1699.Gandalf:GNUapl pteeson$ cd tru

Startup with command line parameters....

Hi Jürgenl:I was trying out how to startup APL using command line parameters. My first attempt worked:Last login: Sun Jun  4 13:43:24 on ttys000Gandalf:~ pteeson$ apl -l 37….. Command Line Parms test 1.txt.pdf Description: Adobe PDF document But I had to know that LID_startup was  enum 37. (UserPr

Re: Startup with command line parameters....

posal. The logging facilities are already > described in the GNU-APL-Designers-Guide.html and > I have added a note concerning -l 37. Also: > > apl --help > > mentions it, although it could be missed there due to the many > command line options. > > SVN 1705. > > Be

Re: Building GNU APL with clang

Yes many times on my Apple Mac which runs macOS. > On Oct 2, 2023, at 8:07 PM, Russtopia wrote: > > Hello, See topic. > > I would rather not, but in this case I am trying to re-build GNU APL in > Termux on my newer Android phone, and Termux decided some time ago to remove > gcc entirely from

Re: Hot Footer

Oh my!FWIW in 1955 I emigrated from the UK to Canada. My first job was as a clerk with Underwood Typewriter. But during my lunch 1/2 hour I had to learn how to use an Olivetti Underwood Sundstrand adding machine. In order to add up a pile of invoices….. look at the invoice for the amount whi

[Bug-apl] Building on OS X 10.8.5 Mountain Lion

system. Do I need to set an environment var for gcc and cc? Where is the proper place to do this? In configure.ac? AC_PROG_CXX AC_PROG_CC Or some other way? Sorry to be so ignorant of naked unix but it's never been necessary for me to dig that deep. Thanks and respect…. Peter Teeson (former

Re: [Bug-apl] Building on OS X 10.8.5 Mountain Lion - partly resolved….

On 2014-03-11, at 4:30 PM, Peter Teeson wrote: > Mac Pro Desktop dual quad core CPU's, Mountain Lion OS X 10.8.5 > > I DL'd the 2014-01-13 APL 1.2 tar.gz and did ./configure. > Blew up because of > configure:2767: checking for gcc > configure:2797: result: no >

Re: [Bug-apl] Building on OS X 10.8.5 Mountain Lion - SOLVED and How to setup your keyboard.

Sorry to intrude but….. Is there a better list to share these steps about using your lovely implementation on Mac? I can make a better formatted form (via TeX if desired). > The solution is much simpler. For Xcode 5: > Launch Xcode > Go to Xcode menu and select Preferences and Downloads > Choose

Re: [Bug-apl] Building on OS X 10.8.5 Mountain Lion - SOLVED and How to setup your keyboard.

/ Jürgen > > > On 03/13/2014 10:12 PM, Peter Teeson wrote: >> Sorry to intrude but….. >> Is there a better list to share these steps about using your lovely >> implementation on Mac? >> I can make a better formatted form (via TeX if desired). >> >>&g

[Bug-apl] GNU APL on Mac

Hi folks: Attached is a small 12 page guide to help installing GNU APL on a Macintosh. Please review it and help to make it better by letting me know how. Thanks and respect…. Peter

Re: [Bug-apl] clang warning

Updated to revision 211. ../GNUAPL/apl-svn/src/UserPreferences.cc:378:1: Control may reach end of non-void function Peter

[Bug-apl] Bug in my knowledge..

This is a bug in my brain but related to GNU APL. Last time I used APL was when I worked at IPSA. The language has been extended since then. I have the ISO Standard and even the IBM APL2 Language Summary & Programming Guide. What can I read for a summary of the differences between the APL I know/

[Bug-apl] clang Warning - revisited

Hi Jürgen: I've been thinking again about this warning and I'm inclined to agree with it. ..MyProjects/GNUAPL/apl-svn/src/UserFunction.cc:1191:10: Comparison of constant 10 with expression of type 'Function_Line' is always true if (l < 10) ucs.append(UNI_ASCII_SPACE); These suggestions e

[Bug-apl] 2 more clang Warnings + 3 similar ones

../apl-svn/src/Token.cc:545:11: 5 enumeration values not handled in switch: 'TC_L_CURLY', 'TC_R_CURLY', 'TC_MAX_PHRASE_2'… ../apl-svn/src/Token.cc:601:11: 5 enumeration values not handled in switch: 'TC_L_CURLY', 'TC_R_CURLY', 'TC_MAX_PHRASE_2'… Should there be a default label in the switch? You

[Bug-apl] clang Warning

/bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include -rdynamic -g -O2 -MT file_io.lo -MD -MP -MF .deps/file_io.Tpo -c -o file_io.lo file_io.cc libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include -rdynamic -g -O2 -MT file_io.

[Bug-apl] Good news..

As of APL 1.3 6401 -- For OS X both Mountain Lion 10.8.5 & Mavericks 10.9.2 ./configure --disable-nls ; make clean ; make /apl-svn/src/file_io.cc:113:41: Expression result unused Input.cc:106:42: warning: conversion from string literal to 'char *' is deprecated [-Wdeprecated-writable-strings]

[Bug-apl] 2 questions wrt editing my programs

(1) Where is docn for the built in function editor when running in terminal mode? (I have the IBM manuals - should I be looking there? Also I am not familiar with emacs or vi) (I'm only familiar with the IPSA one) (2) Can I use an external text editor and interface with quad FX? Because I now w

Re: [Bug-apl] 2 questions wrt editing my programs

Heh Heh…. Yes I do know about emacs mode and your contribution….. respect…. Peter On 2014-04-21, at 6:33 PM, Peter Teeson wrote: > (1) Where is docn for the built in function editor when running in terminal > mode? > (I have the IBM manuals - should I be looking there? Also I am not

Re: [Bug-apl] 2 questions wrt editing my programs

Thanks Jürgen & Elias for your responses. I will explore both approaches. In fact I have downloaded Emacs for OS X from but not yet installed it. As a long time user of BBEdit, a great text editor for Mac, I've also downloaded the free TextWrangler app. It's also fr

Re: [Bug-apl] A call for justification of feature / library / extension proposals (was Re: Tk/Tcl interface)

David's is a thoughtful email which which we should consider without prejudice. The ISO standard makes clear, in chapter 4, what it means to be compliant. When I worked at IPSA Ken Iverson's office was just a couple away from mine. He was very thoughtful of what should be added/extended to the lan

Re: [Bug-apl] A call for justification of feature / library / extension proposals (was Re: Tk/Tcl interface)

Blake said: > "This means creating a quad function to load, execute, and interface with > shared libraries (so/dll/etc). > It also means standard ways of communicating data back and forth" clap clap clap. +1. That's basically the idea of what we did at IPSA. As for the file system it was bui

Re: [Bug-apl] A call for justification of feature / library / extension proposals (was Re: Tk/Tcl interface)

This discussion is and has been healthy and useful - at least to me. Jürgen's point's wrt the open issue of libraries etc gives us good ground to stand on. Are we not all "newbies" wrt GNU APL even those who have a history using APL? I certainly feel that way. Personally there has been an underl

[Bug-apl] Test build re SVN 221

/bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include -rdynamic -g -O2 -MT util.lo -MD -MP -MF .deps/util.Tpo -c -o util.lo util.cc libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include -rdynamic -g -O2 -MT util.lo -MD -MP -MF .

[Bug-apl] Line Editor bug?

As of svn 221 I expected the editor to allow editing of line [1] at position 10. Did I misunderstand? respect…. Peter

[Bug-apl] Bug-apl] APL and text editors- some initial thoughts

Hi Jürgen - I'm back from a mini-break. The ISO Standard Ch 16 p 239 et seq specifically states "The user makes entries on a keyboard, and obtains responses by seeing them presented on a display- device. The combination of a keyboard and a display-device is intended to represent, abstractly, a te

Re: [Bug-apl] APL and text editors- some initial thoughts

Hi Elias: Firstly I am totally agnostic as to which text editor should be used. I don't even understand why there should be an Emacs mode. But since you said it's actually generic maybe we can change it's name to more clearly reflect its generic nature? External Editor Mode? Just a fleeting th

Re: [Bug-apl] Test build re SVN 221

Hi Jürgen: > "your compiler apparently pretends to be g++" ROTFLOL Yes no need to push this any further….. respect… Peter

[Bug-apl] Proposal wrt experimental code

Hi Jürgen: This is a proposal for a mechanism to allow experimental code but still distribute it without becoming part of the "officially supported" code base. My reasons for proposing this have been stated previously but to recap: "Experimental code too often becomes the de facto released code

Re: [Bug-apl] Proposal wrt experimental code

Hi Jürgen: So sorry but we are not understanding each other on this. I apologize for my inability to state it more clearly. This is a long reply but I'm trying to explain it with words. Too bad we can't sit down over a mug of beer (or a cup of tea) and discuss it IRL. My proposal is NOT specific

[Bug-apl] Compiler Warnings after ./configure DYNAMIC_LOG_WANTED=yes

Hi Jürgen: ..GNUAPL/apl-svn/src/Logging.cc:32:11: Enumeration values 'LID_NONE' and 'LID_MAX' not handled in switch ..GNUAPL/apl-svn/src/Logging.cc:42:11: Enumeration values 'LID_NONE' and 'LID_MAX' not handled in switch ..GNUAPL/apl-svn/src/Logging.cc:47:1: Control may reach end of non-void func

[Bug-apl] Linker error libstdc++ vs Libc++

Sigh….. Tracking down something in nabla I decided to start absolutely clean and did a new SVN checkout. I did the usual ./configure followed by make and got this: ….. Undefined symbols for architecture x86_64: "_libintl_bindtextdomain", referenced from: _main in apl-main.o "_libintl_get

Re: [Bug-apl] Linker error libstdc++ vs Libc++

his can often be cured by eg. > > CXX=mycompiler ./configure > > see INSTALL for more details. An alternative could be ./configure > --without_readline or playing around with > --with-libintl-prefix= if you have both library variants installed. > > /// Jürgen >

Re: [Bug-apl] Linker error libstdc++ vs Libc++

We probably want to do that at some time anyway but IMHO a simpler solution is to make the default in configure be --without-nls. Particularly in view of Jürgen's comments. So if somebody wants NLS they have to be intentional. Either way it's no big deal to just add it or remove it at ./configur

Re: [Bug-apl] Linker error libstdc++ vs Libc++ (maybe) SOLVED

Previously I said "OK I spent some time digging around and maybe I understand a bit more." and also "Not totally confident that I have analyzed this correctly. What do you think?" Well here is a better analysis which I do feel more confident about. The version of gettext I had previously instal

Re: [Bug-apl] native function lib_file_io reload not working

Hi Jürgen: Never noticed the link before but I just printed it out for thoughtful reading. respect…. Peter On 2014-05-08, at 10:25 AM, Juergen Sauermann wrote: > Hi, > > I have written a proposal earlier but haven't received any comments so far. > > The document is available here: > http://w

Re: [Bug-apl] )SAVE should show WSID

I think you are correct Blake. IIRC @ IPSA we used UTC internally for things saved to HD. But displayed local time on the Terminal which was an IBM 2741 with an APL golf ball. (FWIW We also had a really really precise external clock custom built for us which we used for date/time things rather

[Bug-apl] TERM env var not getting set

Using Mac OS X 10.8 and the Apple Xcode 5.1.1 development IDE The first few lines in main are: int main(int argc, const char * _argv[]) { { // make curses happy // const char * term = getenv("TERM"); if (term == 0 || *term == 0) setenv("TERM", "dumb", 1); } bool log_st

[Bug-apl] Error after make developer

I did ./configure ; make develop; make /Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/src/Value.cc:1319:9: Goto into protected scope Value.cc:1319:9: error: goto into protected scope goto complete; ^ const Cell * C = &get_ravel(0); ^ uint32_t error_count = 0;

Re: [Bug-apl] TERM env var not getting set

gt; Q(getenv("TERM")) > > (needs recompile) before: > > bool log_startup = false; > > I guess your debugger is fooling you. > > /// Jürgen > > > On 05/21/2014 09:59 PM, Peter Teeson wrote: >> Using Mac OS X 10.8 and the Apple Xcode 5.1.1 develop

[Bug-apl] stdin still echoed to stdout even with --noCIN

In Xcode I pass TERM=xterm-256color as an env var. This is the value Terminal uses. Also --noCIN as an option at launch time to turn off echoing stdin. Set breakpoint here in UserPreferences.cc: else if (!strcmp(opt, "--noCIN")) { do_not_echo = true;

Re: [Bug-apl] stdin still echoed to stdout even with --noCIN

Hi Jürgen: Thanks for your suggestion but CinOut::overflow(int c) { Q(uprefs.echo_current_file()); if (!uprefs.echo_current_file()) return 0; CInOut::overflow(int c) is never called. Please see my next post. Peter On 2014-05-23, at 8:43 AM, Juergen Sauermann wrote: > Hi Peter, >

Re: [Bug-apl] Boehm garbage collector

FWIW Apple moved away from GC and instead uses ARC <=> Automatic Reference Counting. In my experience it has radically reduced the MRR <=> Manual Retain Release effort for the programmer. If anyone is interested here is a link that may be of interest.

[Bug-apl] Is this output incorrect?

Please note the command line options. My question is: Should the following be (a) indented by 6 spaces and (b) Nabla::edit ought to provide line numbering? respect…. Peter

Re: [Bug-apl] Is this output incorrect?

Hi Jürgen: Well please help me properly understand the no_readline function in Input.cc. Because it's called instead of the readline library because of the --rawCIN. I've made comments of my interpretation of the code but am probably wrong. So I'd appreciate any contribution to my very rusty C++.

Re: [Bug-apl] Is this output incorrect?

Thanks Jürgen for correcting my comment. You've prompted me to browse through my venerable copy of Josuttis' The C++ Standard Library. respect… Peter On 2014-06-01, at 8:00 AM, Juergen Sauermann wrote: > Hi Peter, > > almost correct. The first comment should be "// may point to an optional

Re: [Bug-apl] Command::process_line breakup

Well this is an opportunity to bring up something that has been on my mind for some time. My feeling is that a better way to deal with the I/O issue is to have an abstract Class ( or Classes) from which the various I/O implementations can inherit. e.g. Class Input, Class Output or Class InputO

Re: [Bug-apl] GNU APL for Android

Good for you Elias. That is precisely along the lines I am working - build the interpreter as a dll wrapped in the I/O mechanism of your choice. respect… Peter On 2014-06-10, at 6:03 AM, Elias Mårtenson wrote: > I am on vacation right now, so what better time to work on some fun open > sourc

[Bug-apl] Revision 327 minor warning

GNUAPL/apl-svn/src/UTF8_string.cc:273:1: Control reaches end of non-void function

Re: [Bug-apl] Android features

I suggest once again two abstract classes for I/O with virtual methods which can then be inherited from and implemented by the user. This special case patching of fixes is not elegant - to me it is smelly coding. Sorry if I offend but that's my 2¢. Peter On 2014-06-15, at 4:06 PM, Elias Mårte

Re: [Bug-apl] Android features

Input.cc and AndroidInput.cc. > 2. Both use the same Input.hh so that all other source files are no affected. > Not all functions > declared in Input.hh need to be implemented, so AndroidInput.cc. can be > rather simple. > 3. The src/Makefile decides which of the two files shal

Re: [Bug-apl] Android features

least simpler) proposal, in my eyes, is this: > > 1. We use two files Input.cc and AndroidInput.cc. > 2. Both use the same Input.hh so that all other source files are no affected. > Not all functions > declared in Input.hh need to be implemented, so AndroidInput.cc. can be >

Re: [Bug-apl] Can't break out of the middle on a display operation

In Sharp APL (IPSA) we had a "panic int" which interrupted whatever was being computed after a predetermined time. It was inherent to the interpreter because we ran a timesharing system. I don't recall the exact details but it went something like this; 1) Workspace gets swapped in for execution a

Re: [Bug-apl] ISO Component File API preview

On 2014-07-10, at 5:22 PM, Blake McBride wrote: > What I've been trying to convey (and clearly have failed on every attempt so > far) is that an APL component file system must be file-centric. Every APL > component file system that I've worked with or have read about has created a > file to co

Re: [Bug-apl] ISO Component File API preview

Blake McBride wrote: > On Thu, Jul 10, 2014 at 4:49 PM, Peter Teeson wrote: > > On 2014-07-10, at 5:22 PM, Blake McBride wrote: >> What I've been trying to convey (and clearly have failed on every attempt so >> far) is that an APL component file system must be file-c

[Bug-apl] Warning SVN 371 on OS X

/Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/src/APserver.cc:609:1: Control reaches end of non-void function #else int open_UNIX_socket(const char * listen_name) { cerr << "*** this platform does not support address family AF_UNIX!"; } #endif

Re: [Bug-apl] TextWrangler, Emacs Key Bindings and GNU APL

example, ls -la | edit If you just type edit with no parameters, the tool will accept STDIN from the terminal; type Control-D (end-of- file) to terminate and send it to TextWrangler. On 2014-07-20, at 3:36 PM, Peter Teeson wrote: > Bare Bones Software makes a free text editor for Macint

[Bug-apl] Build error SVN 403 on OS X 10.8.5

Did a brand new checkout, ./configure, make /Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/src/FloatCell.cc:393:39: Call to 'pow' is ambiguous FloatCell.cc:393:39: error: call to 'pow' is ambiguous const APL_Float z = pow(A->get_real_value(), b);

[Bug-apl] Strange T∆ output... OS X 10.8.5

I launched apl --noColor --silent Version / SVN: 1.3 / 7603 When I trace this line: i←(2|j)/j←⍳×/k←⍴Y it produces this display Please display the tiff because when I copy/paste mail shows this 13579111315 which is not what I see on the Terminal. but it should display this value for i adj[

[Bug-apl] Determining data type...

I feel pretty stupid. Looked in the APL2 IBM manual but do not understand how to determine the data type of a variable. Neither the primitives nor the Quads sparked the answer in my brain. It must be something pretty obvious but not to me right now. So if I have a function FOO X how do I determi

Re: [Bug-apl] Determining data type...

zero imaginary part. > > Finally, you can compare a number's floor to the number itself to > determine whether the value is integer or real. > > Not knowing your application, I have to warn you that you shouldn't use > these tests to infer anything about APL's storage. All

Re: [Bug-apl] Determining data type...

are right. Here are the available symbols: > > ⍵ - Right-hand argument > ⍺ - Left-hand argument > ⍹ - Right-hand function (the lambda is an operator) > ⍶ - Left-hand function (the lambda is an operator) > χ - Index > > Regards, > Elias > > > On 1 August 2014

Re: [Bug-apl] Determining data type...

Thank you Kacper for both your original reply and this clarification. My eyesight is not what it used to be… we persevere however. respect… Peter On 2014-07-31, at 10:53 PM, Kacper Gutowski wrote: > On 2014-07-31 22:49:06, Peter Teeson wrote: >> David used theta as well. Is tha

Re: [Bug-apl] GNU APL on a Mac

Back in March this year I wrote up a small guide which you can find in the doc folder. It's title is APL-on-Macintosh.pdf Should you run into issues I may be able to help. And of course if you find errors in the pdf or poorly written bits please let me know and I will correct it. respect… Pe

Re: [Bug-apl] GNU APL on a Mac

ally great job! > > Thanks! > > Blake > > > > On Fri, Aug 1, 2014 at 12:45 PM, Peter Teeson wrote: > Back in March this year I wrote up a small guide which you can find in the > doc folder. > It's title is APL-on-Macintosh.pdf Should you run into issues I ma

[Bug-apl] build warning on OSX

I did a brand new SVN co and then did ./configure and got this warning file://localhost/Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/workspaces/SCRIPT.apl: warning: Missing file: /Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/workspaces/SCRIPT.apl is missing from working copy. Pete

Re: [Bug-apl] build warning on OSX

Makefile and Makefile.am I'm confused…. Peter On 2014-08-05, at 6:41 AM, Juergen Sauermann wrote: > Hi Peter, > > I guess you accidentally deleted the file or did the 'svn update' from the > src subdir? > > /// Jürgen > > > On 08/04/2014 09:51 PM

Re: [Bug-apl] Creating a new release

Checked out , built and tested on both OS X 10.8.5 and 10.9.4 with no errors or warnings (except that I do not have Postgres on 10.9.4). On 2014-08-05, at 3:16 PM, David Lamkins wrote: > Tested on one of my Fedora 20 systems, both by an update to my existing work > dir and a fresh SVN checkout

Re: [Bug-apl] GNU APL 1.4 released

Great job Jürgen..and Elias, Blake, and David. respect… Peter On 2014-08-07, at 1:57 PM, Juergen Sauermann wrote: > Hello, > > I am happy to announce that GNU APL 1.4 has been released. > > This release contains: > > * an interface to mySQL and Postgres databases (thanks to Elias) > > *

[Bug-apl] APL fill elements

Is there a nice way to set the fill element for arrays? Right now it's 0 for numeric and ' ' for character. Because my function, that is deliberately ⎕IO agnostic, produces an m by n array of different length vectors as a result of using X←(⊂matrix)foo¨matrix. These vectors are certain indices i

Re: [Bug-apl] APL fill elements

t; 42 42 1 1 1 > 42 42 1 1 1 > 42 42 1 1 1 > 1 1 1 1 1 > > /// Jürgen > > > On 08/09/2014 08:15 PM, Peter Teeson wrote: >> Is there a nice way to set the fill element for arrays? >> Right now it's 0 for numeric and ' ' for character. >> &

[Bug-apl] A word of warning…re posted DyalogAlt.keylayout for Mac OS X

The currently posted layout dated 2011-04-13 at 16:09 (GMT +1:00) (edited by Ukelele version 2.1.5) has does not have the glyphs that were in a later version (which was the one previously posted) dated 2011-09-29 at 14:26 (GMT +1:00) (edited by Ukelele version 2.1.7) The missing glyphs are in

[Bug-apl] OS X DyalogAlt.keylayout mappings to add...

Hi Blake: In your email of 5 Aug your mentioned the following missing mappings in the apl.xmodmap. > χ ⍹ ⍶ ⍷ ⍨ ¥ ⍸ ⍣ ⌷ ⍥ ¢ £ ⍙ The DyalogAlt.keylayout for OS X dated 2011-09-29 at 14:26 (GMT +1:00) (edited by Ukelele version 2.1.7) contains the following in the Shift + Alt plane > ⍷ ⍨ ⍸ ⍣ ⌷ ⍥

[Bug-apl] OS X link to DyalogAlt.keylayout is to older version than previously

I'm sure you know. Please correct this and restore the later dated file. Thanks & respect Peter Teeson

Re: [Bug-apl] OS X DyalogAlt.keylayout mappings to add...

Thanks Blake - added that one. When you say keyboard definitions I interpret that to mean for use with xkbcomp. Since it is not part of a standard OS X install and requires running X I decided to go with Apple's use of XML. Furthermore that's what Dyalog has done. Also Readme-3 in the keyboard se

Re: [Bug-apl] OS X DyalogAlt.keylayout mappings to add...

pealing for that > reason. I'd like to get one of my Mac's up with GNU APL, but I haven't done > it yet. > > Thanks for your work on the Mac files!! > > Blake > > > On Mon, Aug 11, 2014 at 7:34 PM, Peter Teeson wrote: > Thanks Blake - added that

Re: [Bug-apl] OS X DyalogAlt.keylayout mappings to add...

ter On 2014-08-11, at 10:06 PM, Peter Teeson wrote: > Hmmm interesting… I don't think that would be too hard to do. > Thanks for the idea. I'll check it out tomorrow. > Peter > On 2014-08-11, at 9:37 PM, Blake McBride wrote: >> Dear Peter, >> I think the GN

[Bug-apl] MacAplAlt.keylayout & updated Installation Guide

I have a Mac keyboard layout available as well as an updated Installation Guide. May I suggest that a new folder be created in /support-files named OS X-keyboard? The Guide provides manual instructions on how to install it - a simple drag and drop to either /Library/Keyboard Layouts or preferab

Re: [Bug-apl] MacAplAlt.keylayout & updated Installation Guide

Hi Jürgen: Thanks very much. In the MacAplAlt.keyboard I placed a Comment making it GPL'd (same as the install guide). That way it's not proprietary. IMPO I believe we should place ⍙ at Shift+Alt+h (since Alt+h is where ∆ js placed) and that's what I've done for MacAplAlt. Also unless there is a

[Bug-apl] 8 Warnings latest SVN

8 Warnings latest SVN /Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/src/Output.cc:255:19: Unsequenced modification and access to 'errors' /Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/src/Output.cc:256:19: Unsequenced modification and access to 'errors' /Volumes/Data/Development/MyPro

[Bug-apl] What is the correct key code for diamond?

The subject says it all. I have a glyph setup for my MacAplAlt but it must be the wrong key code. Because if I use it I get Offending token…..SYNTAX ERROR. So what is the correct one to use please? Thanks…. Peter

Re: [Bug-apl] What is the correct key code for diamond?

Great thanks that fixed it. On 2014-09-13, at 6:58 PM, David B. Lamkins wrote: > U+25CA (from src/Avec.def)

Re: [Bug-apl] What is the correct key code for diamond?

It could also be that there is another diamond around. If that is the case > then please let me know > its unicode and I will add it to the table of alternative characters in > Avec::map_alternative_char(). > > /// Jürgen > > > On 09/14/2014 04:57 AM, Peter Teeson wrot

[Bug-apl] Why do I hit this SYSTEM LIMIT?

c←⍳9 d←'c',('n',⊃⍕¨c),'←'),'⍳'),'0'),' '),'◊' SYSTEM LIMIT (prefix length) d←'c',('n',⊃⍕¨c),'←'),'⍳'),'0'),' '),'◊' ^ ^ but this is OK? d←((('c',('n',⊃⍕¨c),'←'),'⍳'),'0'),' ' I don't see prefix length in ⎕SYL. I don't u

[Bug-apl] errors in latest SVN

/Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/src/Parallel.cc:181:1: Unknown type name 'cpu_set_t' /Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/src/Parallel.cc:197:55: Use of undeclared identifier 'cpu_set_t' /Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/src/Parallel.cc:323:1:

Re: [Bug-apl] Another OSX compile error

/Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/src/PrintBuffer.cc:125:6: Variable length array of non-POD element type 'PrintBuffer' /Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/src/PrintBuffer.cc:188:6: Variable length array of non-POD element type 'PrintBuffer'

[Bug-apl] Macintosh compile errors and warnings SVN 581

Hi Jürgen: Congratulation on the 1.5 release…. So to keep you busy here are some issues on Mac OS X 10.8.5 respect…. Peter Shell Script Invocation Error Group /Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/Workspace.hh::257257::2626:0: Non-ASCII characters are not allowed outside of liter

Re: [Bug-apl] Macintosh compile errors and warnings SVN 582

Hi Jürgen: Almost fixed… but some new errors & warnings…:-} Peter On 2015-03-31, at 10:10 AM, Juergen Sauermann wrote: > Hi Peter, > > thanks, should be fixed in SVN 582. > > /// Jürgen SVN 582 GNUAPL Group Shell Script Invocation Error Group /Volumes/Data/Development/MyProjects/GNUAPL/apl-s

Re: [Bug-apl] Macintosh compile errors and warnings SVN 583

GNUAPL Group Shell Script Invocation Error Group /Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/src/TempFileWrapper.cc:45:5: No matching function for call to 'strcpy' /Volumes/Data/Development/MyProjects/GNUAPL/apl-svn/src/TempFileWrapper.cc:47:10: No matching function for call to 'mkstemp'

  1   2   3   >