.
Namaste,
- Dennis
-Original Message-
From: Brick Ma [mailto:brickman...@gmail.com]
Sent: Wednesday, April 8, 2015 04:30
To: dev; Dennis Hamilton
Subject: Re: ruby uno to control openoffice
Hi,Dennis
I replace openoffice 3.4.1 to openoffice4.1.1.
static const ::sal_Int16 OPTIONAL
do not fail.
>>
>> There may be clues there.
>>
>> - Dennis
>>
>> -Original Message-
>> From: Brick Ma [mailto:brickman...@gmail.com]
>> Sent: Thursday, April 2, 2015 08:47
>> To: dev; Dennis Hamilton
>> Subject: Re: ruby uno to
s for any of
> those capitalized names that do not fail.
>
> There may be clues there.
>
> - Dennis
>
> -Original Message-
> From: Brick Ma [mailto:brickman...@gmail.com]
> Sent: Thursday, April 2, 2015 08:47
> To: dev; Dennis Hamilton
> Subject: Re: ruby
.
There may be clues there.
- Dennis
-Original Message-
From: Brick Ma [mailto:brickman...@gmail.com]
Sent: Thursday, April 2, 2015 08:47
To: dev; Dennis Hamilton
Subject: Re: ruby uno to control openoffice
I wrote a line(#define OPTIONAL OPTIONAL) in PropertyAttribute.hdl.
It seems works
elsewhere that are undetected because they do not cause a
>> syntax error.
>>
>> I am not where I can look right now. Nose around. There should be some
>> related definitions in the same part of the source tree.
>>
>> - Dennis
>>
>> -Original Mes
essage-
> From: Brick Ma [mailto:brickman...@gmail.com]
> Sent: Monday, March 30, 2015 08:06
> To: dev; dennis.hamil...@acm.org
> Subject: Re: ruby uno to control openoffice
>
> But with the same PropertyAttribute.hdl i had built c++ sample
> DocumentLoader.cxx,and it works .
&g
: Re: ruby uno to control openoffice
But with the same PropertyAttribute.hdl i had built c++ sample
DocumentLoader.cxx,and it works .
How can i disable this feature of pre-processor
-Brick
On Sun, Mar 29, 2015 at 11:56 PM, Dennis E. Hamilton <
dennis.hamil...@acm.org> wrote:
> It app
But with the same PropertyAttribute.hdl i had built c++ sample
DocumentLoader.cxx,and it works .
How can i disable this feature of pre-processor
-Brick
On Sun, Mar 29, 2015 at 11:56 PM, Dennis E. Hamilton <
dennis.hamil...@acm.org> wrote:
> It appears that OPTIONAL is defined to empty string in
It appears that OPTIONAL is defined to empty string in a pre-processor
definition.
This is probably a conflict with use of OPTIONAL as a way of controlling code
inclusion and not as name of a feature in a bit flag [;<).
- Dennis
-Original Message-
From: Brick Ma [mailto:brickman...@
