Giter VIP home page Giter VIP logo

Comments (8)

joa-quim avatar joa-quim commented on May 29, 2024

Hmm, all tests are in their own directory with that module name. Why making it different for the ``*.-l2s.sh` tests? I prefer to have them where they are.

from gmt.

seisman avatar seisman commented on May 29, 2024

The main reason is, these tests work only when USE_COMMON_LONG_OPTIONS and USE_MODULE_LONG_OPTIONS are defined. When they're not defined, these tests should be excluded. However, the current layout (e.g., having psbasemap-l2s.sh in the psbasemap directory) makes it difficult to exclude these directory. Instead, if all l2s tests are located in the test/long2short directory, we just need to exclude the whole test/long2short directory.

from gmt.

joa-quim avatar joa-quim commented on May 29, 2024

OK, but probably what we should do is to make the USE_COMMON_LONG_OPTIONS and USE_MODULE_LONG_OPTIONS the default now. The work is mostly done and does not interfere with the rest. What is needed is to document them (big task).

from gmt.

joa-quim avatar joa-quim commented on May 29, 2024

I we can close this now, I think.

from gmt.

seisman avatar seisman commented on May 29, 2024

I still prefer to move all l2s tests into a separate test directory, since these tests test the codes in gmt/src/longopt rather than the functionality of individual modules.

from gmt.

joa-quim avatar joa-quim commented on May 29, 2024

In fact, even the fact that the longopt is currently in a bunch of separate headers was discussed at the beginning of this work and the idea was to revise that decision at the end. For example I would rather have each of those .h inserted directly inside the corresponding C code. Anyway, I see no advantage in joining all the l2s tests in a single directory as that makes needlessly harder to find a specific test as comparing to finding it in the directory where all other tests of that module reside.

from gmt.

seisman avatar seisman commented on May 29, 2024

In fact, even the fact that the longopt is currently in a bunch of separate headers was discussed at the beginning of this work and the idea was to revise that decision at the end. For example I would rather have each of those .h inserted directly inside the corresponding C code.

Makes sense to me. Closing.

from gmt.

joa-quim avatar joa-quim commented on May 29, 2024

Perfect thanks, then one of these days I'll start the .h integration move but we'll have to take care to leave room for the missing supplements longoptions.

from gmt.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.