Mercurial > hg > xemacs-beta
view etc/toolbar/info-def-xx.xpm @ 5575:89cb6a66a61f
Force unfolding of (funcall #'(lambda () ...) if optimising, bytecomp.el.
lisp/ChangeLog addition:
2011-10-03 Aidan Kehoe <kehoea@parhasard.net>
* bytecomp.el (byte-compile-funcall):
Sometimes the optimizer shirks its responsibility and doesn't
unfold a lambda when it should. Do this here, if optimization is
turned on; this makes inlining labels more consistent and
trustworthy.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Mon, 03 Oct 2011 19:39:01 +0100 |
| parents | 7910031dd78a |
| children |
line wrap: on
line source
/* XPM */ /* This file is part of XEmacs. XEmacs is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. XEmacs is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with XEmacs. If not, see <http://www.gnu.org/licenses/>. */ static char * info[] = { "28 28 2 1", "X c Gray75 s backgroundToolBarColor", "o c Gray60", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXoXXXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXoooooooXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXXXoXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXooooooXXXXXXXXXXXX", "XXXXXXXXXoooooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXoooooooXXXXXXXXXXX", "XXXXXXXXXoooooooooXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};