Re: CInt and function pointers...

Hi !

> I can give you information where it is possible.  I am afraid you are probably underestimating amount of effort needed to realize what you'd like to acomplish. 


That's ok, I'm learning new things and techniques. C++ scripting is only intermediate step for me, at the end I would like to get
new (programming + natural)  language in place - some ideas can be found here:

http://simplelanguage.wikidot.com/local--files/forum:start/NewLanguage_v0_2.ppt


I'm already similar with gcc's abstract syntax trees, and compilers in that sense.

Ok, I'll try to dig up next questions, after I'll hit into problems.

--
Have a nice day!
Tarmo.


----- Original Message -----
From: "gotom@..." <gotom@...>
To: Tarmo Pikaro <tapika@...>
Cc: "cint@..." <cint@...>
Sent: Saturday, January 14, 2012 6:27 PM
Subject: Re: [CINT] CInt and function pointers...

Hello Tarmo,

That is already provided.

#ifdef __CINT__
// CINT specific code
#endif
#ifdef G__ROOT
// CINT used with ROOT specific code
#endif

I can give you information where it is possible.  I am afraid you are probably underestimating amount of effort needed to realize what you'd like to acomplish.

Thank you
Masaharu Goto


---- Tarmo Pikaro <tapika@...> さんは書きました:
> Hi !

> At this moment, I am an active user of CINT and ROOT, however not active for support and enhancement.? Supporting multiple applications + multiple platforms and continuing compiler version up turned out?
> to be too much, together with my other work.? I am still using old Visual C++6.0/7.2 on Windows. gl and Win32API are the most tricky libraries among all.


This is so typical - you're considering youself as support personnel for all compilers and platforms, meanwhile I think you should take different perspective -?
you're developing master codeline, and visual c++ is a clue to your script. :-) ?I would propose to make special kind of define which identifies CINT scripter
and allow developers to patch existing environments to hide incompatibilities. For example:

windows.h:
...
void
#ifdef CINT
? ? __stdcall
#endif
? ? ? myfunc(void);
...

however - this is not always doable - hit already against incompatibilities with call conventions.

Anyway - are you willing to assist / help me if I'll take a swim into cint source code ?
(I'll analyze it for suitability for further development, but after that I don't see any problem).

It would be also good if you could give me good contacts to chat directly - skype id's / etc...

We could use this forum as well, but for moderated information.

?
--
Have a nice day!
Tarmo.


----- Original Message -----
From: "gotom@..." <gotom@...>
To: Tarmo Pikaro <tapika@...>
Cc: cint@...
Sent: Friday, January 13, 2012 6:51 AM
Subject: Re: [CINT] CInt and function pointers...

Hi Tarmo,

Thank you very much for your remark.?
I needed such tool as a user and happened to be the one who actually create it.

I used to support CINT and did a lot of enhancements.
At this moment, I am an active user of CINT and ROOT, however not active for support and enhancement.? Supporting multiple applications + multiple platforms and continuing compiler version up turned out to be too much, together with my other work.? I am still using old Visual C++6.0/7.2 on Windows. gl and Win32API are the most tricky libraries among all.

Instead, I am using ROOT as multiplatform graphics, database and house keeping platform. People in CERN and Fermi-Lab are committed to support ROOT/CINT, at least, as long as they operate LHC experiements at CERN which is beyond 2030, I guess.? ROOT looks quite heavy at the beginning, but it is really nice once you learn.

Thank you
Masaharu Goto