Hello to all. I would like to express two personal wishes for 2.0, motivated by
my personal experience with CIL and the recent support to plugins. I think that
plugins should lead to a situation where:
1- complex CIL transformation passes are "unentangled" as compositions of basic
("primitive")
Il giorno 27/ago/2013, alle ore 17.57, Gabriel Kerneis ha scritto:
> Dear all,
>
> I have just merged my work on CIL plugins into the "develop" branch of
> the git repository. This is of interest to anybody who writes his own
> CIL features (previously configured using EXTRA_FEATURES).
This is
Pietro Braione
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are
Il giorno 23/gen/2013, alle ore 12.02, Gabriel Kerneis ha scritto:
> And try --printCilAsIs as suggested.
I misunderstood the meaning of the switch. It works!
Thanks
Pietro
--
Master Visual Studio, SharePoint, SQL, ASP.NET
Hello Gabriel, and thanks for your answer.
Il giorno 23/gen/2013, alle ore 08.54, Gabriel Kerneis ha scritto:
> Hi Pietro,
>
> On Wed, Jan 23, 2013 at 02:38:53AM +0100, Pietro Braione wrote:
>> by transforming x++ in x = x + 1, etc.
>
> CIL already does that for you auto
Hello to everyone. I am not able to find in the documentation the
representation for some kind of statements, i.e., pre/postincrement (++ and
--), and all the operator/assignment statements (with +=, -=, *=, etc). What is
their representation? I need to detect and remove them (by transforming x+
Il giorno 16/nov/2012, alle ore 14.29, Gabriel Kerneis ha scritto:
> On Thu, Nov 15, 2012 at 06:01:50PM +0100, Pietro Braione wrote:
>> Our current idea is to inject some kind of assignment statement to a fubar
>> variable as, e.g., _next_statement_is_relevant = 1, rig
g when we reload the file.
Our current idea is to inject some kind of assignment statement to a fubar
variable as, e.g., _next_statement_is_relevant = 1, right before every
"relevant" statement. Can anyone suggest something be
