User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101
            Thunderbird/24.0.1
MIME-Version: 1.0
References: <20131017141956.GB12033@hzdr.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID:  <52601877.80705@morningstar2.co.uk>
Date:         Thu, 17 Oct 2013 18:03:51 +0100
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: xparse loads graphics
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <20131017141956.GB12033@hzdr.de>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

On 17/10/2013 15:19, Alexander Grahn wrote:
> Consider the following example:
> 
> \documentclass{article}
> \usepackage{xparse}
> 
> \begin{document}
> \ifdefined\includegraphics
>   \typeout{Package `graphics' was loaded.}
> \fi
> \end{document}
> 
> Why das xparse load graphics? What is it used for?
> 
> Alexander

As Lars notes, it's expl3 rather than xparse that loads graphics.

At present, we don't use out 'native' graphics drivers by default for
scaling/rotation/... as part of l3box/l3coffins. As such, we rely on
graphics to do the back-end work. There is an open issue on this,
suggesting we switch to 'native' as standard with the LaTeX2e drivers as
an option. That might be a good idea as it means they get a proper
workout and also as clipping is only available with the native drivers.
The main downside is that we have fewer drivers than graphics does, so
would still need a fall-back for example for tex4ht.
-- 
Joseph Wright