Conditional compilation?

[Denver]

I took a peek on this beta, and you choosed option 3 : the internal preprocessor comes, reads the entire file, then might find the name of another preprocessor in it, then will call the new preprocessor.

Here are my thoughts about it:

;line 452
#Region Input retrieval/validation
;line 566
Retrieve_PreProcessor_Info() ;Hopefully another preprocessor is set here. Or maybe not.
;line 820
#EndRegion Input retrieval/validation
;line 889
#Region Run PreProcessor
;Following #instructions CANNOT (de-)influence what Retrieve_PreProcessor_Info() has already read.
;Unable use :
;   #pragma compile("AutoItExecuteAllowed",\
;                   true)
;Following #instructions CAN influence the rest of the compilation
;Usefull use :
;   #define UNICODE_VERSION_MAJOR 5
;   Local $version = 4
;   #ifdef UNICODE_VERSION_MAJOR
;      if ($version < UNICODE_VERSION_MAJOR) Then MsgBox(0, "Update required.", "Unicode version " & $version & " lower than expected : " & UNICODE_VERSION_MAJOR)
;   #endif
;line 932
#EndRegion Run PreProcessor

I'm not satisfied with this proposal, I'd rather run the internal preprocessor after the external one. That seems a lot of changes, but the only reason why Retrieve_PreProcessor_Info() have to be called before is to extract the $INP_Run_PreProcess_PGM from the script file.

I don't feel comfy in sharing my sourcecode with a #AutoIt3Wrapper_Run_PreProcess_Program="C:\Users\Noémie\Documents\Scripts\AutoIt3\SciTE\AutoIt3Wrapper\preprocessor.exe" attached, and I'm not keen on having to manually set this line to all of my new (moreover existing) script files...
Is there an other way to tell the Wrapper which file to use as preprocessor option ?

Note: I don't recommend the #AutoIt3Wrapper_Run_PreProcess_OutFile option, as it's supposed to be a simple Tempfile anyway. Besides, it is overriding the $ScriptFile_Out's tests, making it possible to have $ScriptFile_In = $ScriptFile_Out when wrongly set.

[Jos]

Seems you havent read my post fully where is stated that autoit3wrapper doesnt perform these type of actions and never will.

As you deemed this proposal unacceptable,  I have reverted the changes and remove the current Beta and wish you success with your endeavour..

Jos

Edited June 28, 2015 by Jos

[Denver]

You don't have to actually revert all the changes you made. You asked me to have a try, so I did. #AutoIt3Wrapper_Run_PreProcess_OutFile option is a wrong idea, #AutoIt3Wrapper_Run_PreProcess_Program is a good one.
I told you why I don't like some parts of your proposal.

We surely can find some place inbetween your implementations and my wishes, can't we ?

Edit : Or, we can't. Since the internal preprocessor is not likely to have any changes before ages, I can maintain my own Retrieve_PreProcessor_Info() manually after a stable release update. Sorry for the inconvenience, please just don't use what I shared before.

Edited June 28, 2015 by Denver
Np.

[Jos]

No worries and am sure you wont be posting any autoit3wrapper versions with your modifications in it to avoid people getting confused.

jos

Edited June 28, 2015 by Jos

[Denver]

Of course. I've editted the first post here to remove my modifications (furthermore based on an out-of-date wrapper).

Love and kisses.

[mLipok]

  On 6/14/2015 at 10:30 AM, Jos said:

You should not try to make your own version of AutoIt3Wrapper as that is modified and distributed by me on a regular basis.
When we feel we should have a pre-processor capability available in AutoIt3Wrapper, I should add an option to shell this external program like I have done for Au3Stripper by adding logic to AutoIt3Wrapper to read some preprocessors, in which you can define your pre-processor program file and the output file created.

EG:

#AutoIt3Wrapper_Run_PreProcess_Program=c:\mypreprocessor.exe
#AutoIt3Wrapper_Run_PreProcess_OutFile=%temp%\preproc.au3

AutoIt3Wrapper could then run this before the au3stripper step and also run au3check against the outputfile from the preprocessor to ensure now errors occur after the pre-process step. It will provide the processed input scriptfile as the first parameter.
In this way people can make their own pre-processor and maintain it independently from any modifications I make in AutoIt3Wrapper.

Thoughts?

Jos

 

Whether using this I can initially use Au3Stripper, I would like to first use
/StripOnly and /rsln
save a copy so prepared file
and later also on the prepared file
again use Au3Stripper but with this param:
/PreExpand and /RM

thus I would have the smallest possible file, in the form of before and after using: /PreExpand and /RM

 

Edited June 28, 2015 by mLipok

[xerox]

How to use a C preprocessor with AutoIt? Any examples? Thanks.

[Jos]

  On 10/30/2018 at 10:28 AM, xerox said:

How to use a C preprocessor with AutoIt?

Expand  

Why would you think this is possible at all?

Jos

[xerox]

Preprocess a au3 file before its compiled? You're saying that's not possible?