[dev] Re: __attribute__((packed)) for enum

2011-05-19 Thread Niklas Nebel
On 19.05.2011 16:40, tora - Takamichi Akiyama wrote: As you pointed out, the installed font might be one of the factors. Excel files are prepared on Windows while I am trying to open them on CentOS and/or Solaris. Those systems have a different font set. Another point that I have been suspecting

[dev] Re: __attribute__((packed)) for enum

2011-05-19 Thread tora - Takamichi Akiyama
Hi Niklas, Am 18.05.2011 13:44, schrieb tora - Takamichi Akiyama: The motivation of this topic comes from a different point. I have been looking for a way to prevent a well-known phenomenon "A single sheet that fits in a A4 paper with Excel turns into two or four A4 papers with Calc." On 2011

[dev] Re: __attribute__((packed)) for enum

2011-05-18 Thread Niklas Nebel
Am 18.05.2011 13:44, schrieb tora - Takamichi Akiyama: The motivation of this topic comes from a different point. I have been looking for a way to prevent a well-known phenomenon "A single sheet that fits in a A4 paper with Excel turns into two or four A4 papers with Calc." Tweaking nPPTX and nPP

[dev] Re: __attribute__((packed)) for enum

2011-05-18 Thread tora - Takamichi Akiyama
On 2011/05/18 18:06, Niklas Nebel wrote: > Generally, this is a very valid concern. In some places where we found out (or just assumed) that it makes a difference, we currently use smaller integer types directly for member variables, instead of enum. For example, see eCellType in ScBaseCell (sc

[dev] Re: __attribute__((packed)) for enum

2011-05-18 Thread Niklas Nebel
On 18.05.2011 03:40, tora - Takamichi Akiyama wrote: The size of class Impl_Font would reduce to 50 bytes or so from 88 bytes. How big benefits could we get when such structure or class instances are produced in large numbers? Generally, this is a very valid concern. In some places where we fo

[dev] Re: __attribute__((packed)) for enum

2011-05-18 Thread Stephan Bergmann
On Wed, May 18, 2011 at 3:40 AM, tora - Takamichi Akiyama < t...@openoffice.org> wrote: > How big benefits could we get when such structure or class instances are > produced in large numbers? > The "produced in large numbers" (plus "processed in bursts of large chunks," I would say) is the crucia

[dev] Re: __attribute__((packed)) for enum

2011-05-17 Thread tora - Takamichi Akiyama
Hi Stephan, Thank you for your comments. On 2011/05/18 4:11, Stephan Bergmann wrote: > Binary UNO requires that its enums are of specific size, but that should be taken care of by the dummy max-value element in each enum. Likewise for enums in the C/C++ URE ABI. > > Whether smaller enums have

[dev] Re: __attribute__((packed)) for enum

2011-05-17 Thread Stephan Bergmann
On Tue, May 17, 2011 at 8:44 PM, tora - Takamichi Akiyama < t...@openoffice.org> wrote: > Any thoughts? > Binary UNO requires that its enums are of specific size, but that should be taken care of by the dummy max-value element in each enum. Likewise for enums in the C/C++ URE ABI. Whether small