Is using `\input{}` in a user defined package to partition it into smaller ones a correct way?

Question

I am writing my own package called mylisting.sty to format code inclusion for languanges: LaTeX, PSTricks, C#, and XML.

To maintain mylisting.sty cleaner, I make a separate file for each language:

LaTeXSettings.tex for LaTeX,
PSTricksSettings.tex for PSTricks,
CSharpSettings.tex for CSharp, and
XMLSettings.tex for XML.

Is it correct to use \input{} within mylisting.sty to import LaTeXSettings.tex, PSTricksSettings.tex, CSharpSettings.tex and XMLSettings.tex?

Or you have a better method to accomplish this objective?

score 3 · Accepted Answer · answered Jan 12 '11 at 05:32

3

It's OK. You can use whatever file name (or extensions) you like. An extensible method is, like many packages use, to use a set of configuration/definition files. For example, in graphics package macro \Gin@driver is the driver file. The code is used as

\DeclareOption{dvips}{\def\Gin@driver{dvips.def}}
\DeclareOption{pdftex}{\def\Gin@driver{pdftex.def}}
% ...
\input{\Gin@driver}

answered Jan 12 '11 at 05:32

Leo Liu

77,365

Let's use your sample above in our discussion. Do I have to specify ProvideFile{dvips.def} in dvips.def ? – Display Name Jan 12 '11 at 05:56
No, you needn't. See clsguide for more information. – Leo Liu Jan 12 '11 at 06:23
2

but you should. then it is listed in file list which makes sense if one has an error in his code. – Jan 12 '11 at 07:32

Is using `\input{}` in a user defined package to partition it into smaller ones a correct way?

1 Answers1