Re: Large numbers seem not to be parsed properly

2023-01-27 Thread Dr . Jürgen Sauermann
Hi Brian, thanks, fixed in SVN 1645. Best Regards, Jürgen On 1/6/23 3:58 AM, Mr. Brian B. McGuinness wrote: GNU APL2:       12345678909876543210

Re: libapl stdout

2023-01-27 Thread Dr . Jürgen Sauermann
Hi enztec, not sure if this helps, but if I remember correctly (I may not) then the main GNU APL output goes to *stderr* (fd 2) and not to *stdout* (fd 1). The reason is somewhat historic because *stdout* is buffered by default while *stderr* is not (which caused some issues with *stdout* when

Re: libapl stdout

2023-01-27 Thread Chris Moller
For what it's worth, in an ongoing project in use: #include #include #include #include #include "aplexec.h" LIBAPL_error AplExec::aplExec (apl_op_e apl_op, QString &cmd,   QString &outString, QString &errString) {  LIBAPL_error execerr = LAE_NO_ERRO

Re: libapl stdout

2023-01-27 Thread enztec
Chris i don't have qt installed nor do i have your #include "aplexec.h" On Fri, 27 Jan 2023 11:23:08 -0500 Chris Moller wrote: > For what it's worth, in an ongoing project in use: > > #include > > #include > #include > > #include > > #include "aplexec.h" > > LI

Re: libapl stdout

2023-01-27 Thread enztec
Hi Jürgen (i hope you are feeling better - if you need a pint of [blood, beer, ] these quotes are from an fpc programmer who is interested in the libapl/apl interface with fpc - i have no idea how to respond and would love something to respond with quote 1: Things would have been much eas

Re: libapl stdout

2023-01-27 Thread Chris Moller
Qt isn't necessary--that's just the environment I'm working in.  From my example, get rid of the #include line. Here's aplexec.h: #ifndef APLEXEC_H #define APLEXEC_H #include #include #define APL_VARIABLE "([⍙∆a-z][⍙∆_a-z0-9]*)" typedef enum {  APL_OP_EXEC,  APL_O

Re: libapl stdout

2023-01-27 Thread enztec
what do i replace all the qstring with /apl/libapl/c > grepi qstring ./aplexec.h:18:aplExec (apl_op_e apl_op, QString &cmd, ./aplexec.h:19:QString &outString, QString &errString); ./libaplc.c:12:AplExec::aplExec (apl_op_e apl_op, QString &cmd, ./libaplc.c:13:QString &outString, QString &errStri

Re: libapl stdout

2023-01-27 Thread Chris Moller
QString is mmore or less equivalent to the C++ std::string class. On 1/27/23 18:00, enz...@gmx.com wrote: what do i replace all the qstring with /apl/libapl/c > grepi qstring ./aplexec.h:18:aplExec (apl_op_e apl_op, QString &cmd, ./aplexec.h:19:QString &outString, QString &errString); ./libapl

Re: libapl stdout

2023-01-27 Thread enztec
sorry that means nothing to me as to what to replace the qstring below with On Fri, 27 Jan 2023 19:38:51 -0500 Chris Moller wrote: > QString is mmore or less equivalent to the C++ std::string class. > > On 1/27/23 18:00, enz...@gmx.com wrote: > > what do i replace all the qstring with > > >

Re: libapl stdout

2023-01-27 Thread Chris Moller
All of the code below is in the C++ language and std::string is a very basic bit of C++.  If you're not familiar with C++, the string class, stringstream, stringbuf, and so on, the first thing you need to do is get some experience in C++. There is no direct replacement for QString, but std::st