Re: [Plplot-devel] Command-line parsing improvements for both C and Fortran

On 2018-01-07 11:03- Arjen Markus wrote: I can now confirm that it [running examples/fortran/x01f built with local change pl_parse_dynamic = .true.] works for both compilers. Excellent. Now that you have confirmed the "_dynamic" versions of plget_arguments and plparseopts work with modern

Re: [Plplot-devel] Command-line parsing improvements for both C and Fortran

Hi Alan, > -Original Message- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > Sent: Saturday, January 06, 2018 3:30 AM > To: Arjen Markus > Cc: PLplot development list > Subject: RE: Command-line parsing improvements for both C and Fortran > > On 2018-01-05 13:38- Arjen Ma

Re: [Plplot-devel] Command-line parsing improvements for both C and Fortran

On 2018-01-05 08:09- Arjen Markus wrote: First the C example: "x01c -dev wingcc" complains that I did not give the value for the -dev option. If I give other options like "a b c", I get complaints that these are unknown. If I run "x02c -dev wingcc", all works as usual. $ ./x01c -dev wingc

Re: [Plplot-devel] Command-line parsing improvements for both C and Fortran

On 2018-01-05 13:38- Arjen Markus wrote: [...] That [extra printouts of locations reached] limits the possibilities considerably ;). I have narrowed it further to the call of max_cstring_length, but of course this is merely the location where it is noted something is wrong, not necessarily

Re: [Plplot-devel] Command-line parsing improvements for both C and Fortran

Hi Alan, The crash I reported before occurs somewhere between the call to interface_plparseopts(...) and max_cstring_length: $ ./x01f -dev wingcc pl_parse_dynamic = T argv before call to plparseopts(..., PL_PARSE_SKIP) i = 0, argument = ./x01f i = 1, argument = -dev i = 2, argument = w

Re: [Plplot-devel] Command-line parsing improvements for both C and Fortran

Hi Alan, > -Original Message- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > Furthermore, I would appreciate you following the parsing testing advice in > README.release section 2.7.2 to discover which parts of this API work for > gfortran > with version > 4.9.2 (e.g., for

Re: [Plplot-devel] Command-line parsing improvements for both C and Fortran

On 2018-01-03 13:28- Arjen Markus wrote: -Original Message- From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] This commit completes my parsing API changes in bindings/fortran/*.f90 and my changes to examples/fortran/x01f.f90 to test all of these parsing API's. I would appreci

Re: [Plplot-devel] Command-line parsing improvements for both C and Fortran

Hi Alan, > -Original Message- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > > This commit completes my parsing API changes in bindings/fortran/*.f90 and my > changes to examples/fortran/x01f.f90 to test all of these parsing API's. I > would > appreciate your review of my i

Re: [Plplot-devel] Command-line parsing improvements for both C and Fortran

On 2017-12-27 14:26-0800 Alan W. Irwin wrote: Hi Arjen: I have done some further investigation and it appears that even today allocatable character arrays are problematic to a certain extent for Fortran compilers. For example, see . I have no

Re: [Plplot-devel] Command-line parsing improvements for both C and Fortran

On 2017-12-27 09:02- Arjen Markus wrote: I am currently catching up with my e-mail (Christmas is a busy time ...), so this is the first opportunity I have found to respond to your mails. Sure, I will have a look at this. (I even have a generic solution for this type of programming problem,

Re: [Plplot-devel] Command-line parsing improvements for both C and Fortran

Hi Alan, I am currently catching up with my e-mail (Christmas is a busy time ...), so this is the first opportunity I have found to respond to your mails. Sure, I will have a look at this. (I even have a generic solution for this type of programming problem, but it may not be better than your