comp.lang.ada
 help / color / mirror / Atom feed
From: alexander@xn--junivrs-e1a.com
Subject: Resolving Long Filenames for Packages
Date: Wed, 24 Jan 2018 08:23:19 -0800 (PST)
Date: 2018-01-24T08:23:19-08:00	[thread overview]
Message-ID: <ee6543c5-62a4-423d-8c22-30fd7a7bab39@googlegroups.com> (raw)

In my current project, I am making an attempt to elaborate on the means of which a serie of automata operates (and is structured), by building my own version of regular expressions (even though not called that, nor functioning in the exact same way.)

To compile my code I'm using AdaCore's GNAT by running the command `gprbuild`. This means I also have a project file associated with the project, which in and of itself, is looking very basic. It only contains a means of locating the main procedure and executing it.

For my experimental implementation of automata, I have ended up with six different flavors of automata, which I have put in a separate directory, because the names tend to get extremely long:

expressions-parser-automata (the directory)
    expressions-parser-automata-automaton_x.adb
    expressions-parser-automata-automaton_x.ads
    expressions-parser-automata-automaton_y.adb
    expressions-parser-automata-automaton_y.ads
    expressions-parser-automata-automaton_z.adb
    expressions-parser-automata-automaton_z.ads
    expressions-parser-automata-automaton_w.adb
    expressions-parser-automata-automaton_w.ads
    ...

This brings me to my question. Is there a better way to structure an Ada program than this?

Each executive automaton package contains a tagged type and an access type to that tagged type. As such, these files all essentially contain different sub-classes of a super automaton class.

What I'm looking to avoid are the long filenames. Preferably, I would personally want to have a similar structure to what you normally see in modern day programming languages, whereas each package has its own directory dedicated to it (and all its sub-packages), but from what I've seen that's not a thing generally done in Ada.

Once again, how would I generally go about structuring an Ada application to avoid such long filenames? Is there some sort of compiler option I can use? Can I do something about it inside my project (`gpr`) file?

Best regards,

             reply	other threads:[~2018-01-24 16:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24 16:23 alexander [this message]
2018-01-24 17:21 ` Resolving Long Filenames for Packages Robert Eachus
2018-01-24 21:18 ` G. B.
2018-01-25  9:50 ` alexander
2018-01-25 14:13 ` Stephen Leake
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox