Re: Implications of indexing changes for code that calls Fortran

octave-maintainers

From:	John W. Eaton
Subject:	Re: Implications of indexing changes for code that calls Fortran
Date:	Tue, 3 Jan 2017 13:35:15 -0500
User-agent:	Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0

On 01/03/2017 01:25 PM, Olaf Till wrote:

Now I've seen that, contrary to (all?) other files, src/sl_mb05nd.cc
and src/sl_tg04bx.cc had DOS line endings.

Ah, OK, I remember seeing that but I didn't realize it would causetrouble with export/import.

Converted them to unix, and then your changeset did apply, pushed
it. So all your patches are now applied.


Thanks.

jwe

Current Thread

[Next in Thread]

Implications of indexing changes for code that calls Fortran, John W. Eaton, 2017/01/02
- Re: Implications of indexing changes for code that calls Fortran, Nicholas Jankowski, 2017/01/02
  - Re: Implications of indexing changes for code that calls Fortran, John W. Eaton, 2017/01/02
    - Re: Implications of indexing changes for code that calls Fortran, John W. Eaton, 2017/01/02
    - Re: Implications of indexing changes for code that calls Fortran, Olaf Till, 2017/01/03
    - Re: Implications of indexing changes for code that calls Fortran, Olaf Till, 2017/01/03
    - Re: Implications of indexing changes for code that calls Fortran, John W. Eaton, 2017/01/03
    - Re: Implications of indexing changes for code that calls Fortran, John W. Eaton, 2017/01/03
    - Re: Implications of indexing changes for code that calls Fortran, Olaf Till, 2017/01/03
    - Re: Implications of indexing changes for code that calls Fortran, Olaf Till, 2017/01/03
    - Re: Implications of indexing changes for code that calls Fortran, John W. Eaton <=
    - Re: Implications of indexing changes for code that calls Fortran, PhilipNienhuis, 2017/01/07
    - Re: Implications of indexing changes for code that calls Fortran, PhilipNienhuis, 2017/01/03