[Bug-apl] TERM env var not getting set

2014-05-21 Thread Peter Teeson
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

Re: [Bug-apl] Calling Value::print() with different ⎕PW

2014-05-21 Thread Juergen Sauermann
Hi Elias, the *operator<<(ostream & out, const Value & v)* calls *v.print(out)* which then does the line break at *⎕PW*. The cr_formatted below is probably OK but printing it introduces line wrapping. You could have used UCS_string(*cr_formatted) instead of *cr_formatted to avoid that. /// J

[Bug-apl] Package manager nearing initial release - testers/readers requested

2014-05-21 Thread David Lamkins
https://github.com/TieDyedDevil/apl-pkg The APL Package Manager is nearly ready for its initial release. All of the first-release functionality is in place. Documentation is completed. There's a tutorial, a set of demonstration packages, and a roadmap outlining future releases. My intent at this

Re: [Bug-apl] Calling Value::print() with different ⎕PW

2014-05-21 Thread Elias Mårtenson
I tried to specify a different PW like the below, but the with is still limited to something close to 80: const PrintContext pctx( PST_NONE, Workspace::get_PP(), 1000 ); Value_P cr_formatted = Quad_CR::do_CR( cr_level, *value, pctx ); out << *cr_formatted; What did I do wr

Re: [Bug-apl] Calling Value::print() with different ⎕PW

2014-05-21 Thread Elias Mårtenson
Cool. Thanks! And what if I want to output without any quad-CR style at all? (I.e. the default output style ]BOXING none). Is there a cr-style I can use for that? Is it 0? Regards, Elias On 21 May 2014 21:43, Juergen Sauermann wrote: > Hi Elias, > > done in SVN 281. I had to change your Trace

Re: [Bug-apl] Calling Value::print() with different ⎕PW

2014-05-21 Thread Juergen Sauermann
Hi Elias, done in SVN 281. I had to change your TraceData.cc due to the extra argument. I used PrintContext (style + ⎕PP + ⎕PW) instead of print width alone so that other output aspects can be controlled as well. /// Jürgen On 05/21/2014 02:54 PM, Elias Mårtenson wrote: Yes, of course. :-

Re: [Bug-apl] Calling Value::print() with different ⎕PW

2014-05-21 Thread Elias Mårtenson
Yes, of course. :-) I was focused on the other solution to set a custom PW. Obviously adding pw as an argument to do_CR is a better idea. Regards, Elias On 21 May 2014 20:52, "Juergen Sauermann" wrote: > H Elias, > > that sounds more like making the print width a parameter of do_CR() > because

Re: [Bug-apl] Calling Value::print() with different ⎕PW

2014-05-21 Thread Juergen Sauermann
H Elias, that sounds more like making the print width a parameter of do_CR() because the left arg of ⎕CR is already the first argument of do_CR() ? /// Jürgen On 05/21/2014 02:33 PM, Elias Mårtenson wrote: To clarify, What I have is a Value, and all I want to do is to get a string containing

Re: [Bug-apl] Calling Value::print() with different ⎕PW

2014-05-21 Thread Elias Mårtenson
To clarify, What I have is a Value, and all I want to do is to get a string containing the printed form of that Value for a given quad-CR-left-hand-value. I don't want the resulting string to be wrapped (since I'm handling that on the Emacs side). Regards, Elias On 21 May 2014 20:29, Elias Mårte

Re: [Bug-apl] Calling Value::print() with different ⎕PW

2014-05-21 Thread Elias Mårtenson
I mean the number to the left of quad-cr. :-) Regards, Elias On 21 May 2014 20:28, "Juergen Sauermann" wrote: > Hi Elias, > > not sure what you mean by 'CR-level' ? > > /// Jürgen > > > On 05/21/2014 06:32 AM, Elias Mårtenson wrote: > > Hello Jürgen, > > I finally got around to attempting to i

Re: [Bug-apl] Calling Value::print() with different ⎕PW

2014-05-21 Thread Juergen Sauermann
Hi Elias, not sure what you mean by 'CR-level' ? /// Jürgen On 05/21/2014 06:32 AM, Elias Mårtenson wrote: Hello Jürgen, I finally got around to attempting to implement this. What I'm actually doing is to ensure that the output in a trace buffer (that displays the content of a variable in

Re: [Bug-apl] Segmentation fault in zero take on scalar

2014-05-21 Thread Juergen Sauermann
Hi Kacpet, thanks, fixed in SVN 280. /// Jürgen On 05/21/2014 05:47 AM, Kacper Gutowski wrote: 0↑0 SEGMENTATION FAULT -- Stack trace at main.cc:122

Re: [Bug-apl] Complex number display

2014-05-21 Thread Juergen Sauermann
Hi Fred, thanks, fixed in SVN 280. /// Jürgen On 05/21/2014 03:28 AM, Frederick H. Pitts wrote: Hello Juergen, Elias, I think there are still three flies in the "complex number display" ointment. Please see the attached tar file containing a APL test file and a log file generated fr