opencxx-users

RE: [Opencxx-users] OpenC++ gets funding

[Stefan S. <sse...@ar...>]

Hi Grzegorz,

> From: Grzegorz Jakacki [mailto:ja...@ac...]

> If you have any suggestions on how this money can be used to advance 
> OpenC++, please post them on this forum.

was the award being granted because OpenC++ already was ported to the PPC ?
Or as an incentive to port it ? If the latter, shouldn't the money be spent
to help do the port ?

Regards,
		Stefan

[Opencxx-users] OpenC++ gets funding

[Grzegorz J. <ja...@ac...>]

Hi all,

Those of you who follow Linux on Power contest may have noticed,
that OpenC++ qualified as Tier 3 application. For those who don't: the
contest is about porting software to PPC architecture (more info
available at http://www.linuxonpower.com/). Admins of SourceForge-hosted 
projects who agreed to judge PPC ports in the contest were sent iPods as 
a gift from contest sponsor (IBM).

I received this gift (iPod mini 4GB) recently. I think I should not keep 
it for  myself. I consulted Chiba, who agreed, that it would make sense 
to sell it and use the the proceeds towards development and promotion of 
OpenC++.

I have just liquidated the item and $250 thus obtained goes to 
(unofficial) OpenC++ Fund, with myself as self-appointed treasurer.

If you have any suggestions on how this money can be used to advance 
OpenC++, please post them on this forum.

Best regards
Grzegorz

[Opencxx-users] RE: Bugfix for gcc-3.4.2 added to CVS of occ-core

[Vinzenz F. <evi...@we...>]

Hi,

I said something wrong,

If you're using OpenC++ you have to replace the line

and if you're using OpenC++ core you can use the file from CVS

BR

Vinzenz

[Opencxx-users] Bugfix for gcc-3.4.2 added to CVS of occ-core

[Vinzenz F. <evi...@we...>]

Hi,

I added an Bugfix for the compilation problems with gcc 3.4.2 to the 
occ-core CVS modul

There are compilation problems with MetacompilerConfiguration.h in 
opencxx and occ-core, if you got this
problem replace the files:

OpenC++:

opencxx/opencxx/MetacompilerConfiguration.h

OpenC++ Core:

occ-core/occ-core/analyzer/MetacompilerConfiguration.h

with the file in the CVS


Problem occours with following error message:

std::auto_ptr<Opencxx::MetacompilerConfiguration::IteratorIface>]":
 ../opencxx/MetacompilerConfiguration.h:50:   instantiated from here
 /usr/include/c++/3.4/bits/stl_algobase.h:132: error: passing `const 
 std::auto_ptr<Opencxx::MetacompilerConfiguration::IteratorIface>" as 
 `this" argument of `std::auto_ptr<_Tp>::operator 
 std::auto_ptr_ref<_Tp1>() [with _Tp1 = 
 Opencxx::MetacompilerConfiguration::IteratorIface, _Tp = 
 Opencxx::MetacompilerConfiguration::IteratorIface]" discards qualifiers
 make[1]: *** [driver.lo] Error 1
 make[1]: Leaving directory `/usr/src/CVS_DATA/opencxx/opencxx"
 make: *** [all] Error 2


taken from MetacompilerConfiguration.h

         Iterator& operator=(Iterator iter)
         {
             std::swap(impl_, iter.impl_); // <- This line causes the error
             return *this;
         }

I changed it to:
      

         Iterator& operator=(Iterator iter)
         {
             auto_ptr<IteratorIface> tmp = impl_;
             impl_ = iter.impl_;
             iter.impl_ = tmp;

             // std::swap(impl_, iter.impl_); // <- This line causes the error
             return *this;
         }


Now you're either be abled to change the lines by yourself or get the 
File from CVS

BR

Vinzenz Feenstra

Re: [Opencxx-users] Preserve comments and layout

[Grzegorz J. <ja...@ac...>]

Stefan Seefeld wrote:

[...]

>You may have a look into this work at http://synopsis.fresco.org,
>though, I reiterate, regenerating the un-preprocessed code is
>impossible as of now and there are no plans to work on anything
>towards such a feature. 
>  
>
This applies to Synopsis, not OpenC++. Understanding unpreprocessed input is
among goals of OpenC++Core library.

BR
Grzegorz

RE: [Opencxx-users] Preserve comments and layout

[Stefan S. <sse...@ar...>]

Hi Iwan,

From: Iwan Birrer

>I do not only want the comments to be preserved, but also: macros,  
>file/directory structure, includes etc. Actally everything, so the  
>transformed code would be equal to the base code if only a dummy  
>transformation is being made.

What exactly are you trying to do ? 
What you are asking for is generally impossible, as preprocessing
is a separate process. In the context of the synopsis project I'v
managed to retain most of the information you require, but not to
regenerate the original code, but to be able to treat macros as 
first-class citizens in the structure I use to generate code 
documentation and to hyperlink the original code to the docs.

You may have a look into this work at http://synopsis.fresco.org,
though, I reiterate, regenerating the un-preprocessed code is
impossible as of now and there are no plans to work on anything
towards such a feature. 

If you are going to compile the newly generated code you only need
equivalent code, and for that the requirements are much less stringent 
as far as code generation is concerned.

Regards,
             Stefan

[Opencxx-users] BUG with std::auto_ptr comming with g++ 3.4.2

[Vinzenz F. <evi...@we...>]

Hi,

I figured out a bug in OpenC++, MetacompilerConfiguration.h contains an 
breaking compile error:

<mailto:ope...@li...> g++ -DHAVE_CONFIG_H -I. -I. 
-I.. -I. -I.. -g -O2 -MT driver.lo -MD -MP -MF .deps/driver.Tpo -c 
driver.cc  -fPIC -DPIC -o .libs/driver.o
In file included from /usr/include/c++/3.4/backward/strstream:51,
                 from driver.cc:47:
/usr/include/c++/3.4/backward/backward_warning.h:32:2: warning: #warning 
This file includes at least one deprecated or antiquated header. Please 
consider using one of the 32 headers found in section 17.4.1.2 of the 
C++ standard. Examples include substituting the <X> header for the <X.h> 
header for C++ includes, or <iostream> instead of the deprecated header 
<iostream.h>. To disable this warning use -Wno-deprecated.
/usr/include/c++/3.4/bits/stl_algobase.h: In function `void 
std::swap(_Tp&, _Tp&) [with _Tp = 
std::auto_ptr<Opencxx::MetacompilerConfiguration::IteratorIface>]':
../opencxx/MetacompilerConfiguration.h:50:   instantiated from here
/usr/include/c++/3.4/bits/stl_algobase.h:132: error: passing `const 
std::auto_ptr<Opencxx::MetacompilerConfiguration::IteratorIface>' as 
`this' argument of `std::auto_ptr<_Tp>::operator 
std::auto_ptr_ref<_Tp1>() [with _Tp1 = 
Opencxx::MetacompilerConfiguration::IteratorIface, _Tp = 
Opencxx::MetacompilerConfiguration::IteratorIface]' discards qualifiers
make[1]: *** [driver.lo] Error 1
make[1]: Leaving directory `/usr/src/CVS_DATA/opencxx/opencxx'
make: *** [all] Error 2


In my opinion it is the new std::auto_ptr which, afaik, has been modified.


BR

Vinzenz Feenstra

[Opencxx-users] BUG with std::auto_ptr comming with g++ 3.4.2

[Vinzenz F. <evi...@we...>]

Hi,

I figured out a bug in OpenC++, MetacompilerConfiguration.h contains an 
breaking compile error:

<mailto:ope...@li...> g++ -DHAVE_CONFIG_H -I. -I. 
-I.. -I. -I.. -g -O2 -MT driver.lo -MD -MP -MF .deps/driver.Tpo -c 
driver.cc  -fPIC -DPIC -o .libs/driver.o
In file included from /usr/include/c++/3.4/backward/strstream:51,
                 from driver.cc:47:
/usr/include/c++/3.4/backward/backward_warning.h:32:2: warning: #warning 
This file includes at least one deprecated or antiquated header. Please 
consider using one of the 32 headers found in section 17.4.1.2 of the 
C++ standard. Examples include substituting the <X> header for the <X.h> 
header for C++ includes, or <iostream> instead of the deprecated header 
<iostream.h>. To disable this warning use -Wno-deprecated.
/usr/include/c++/3.4/bits/stl_algobase.h: In function `void 
std::swap(_Tp&, _Tp&) [with _Tp = 
std::auto_ptr<Opencxx::MetacompilerConfiguration::IteratorIface>]':
../opencxx/MetacompilerConfiguration.h:50:   instantiated from here
/usr/include/c++/3.4/bits/stl_algobase.h:132: error: passing `const 
std::auto_ptr<Opencxx::MetacompilerConfiguration::IteratorIface>' as 
`this' argument of `std::auto_ptr<_Tp>::operator 
std::auto_ptr_ref<_Tp1>() [with _Tp1 = 
Opencxx::MetacompilerConfiguration::IteratorIface, _Tp = 
Opencxx::MetacompilerConfiguration::IteratorIface]' discards qualifiers
make[1]: *** [driver.lo] Error 1
make[1]: Leaving directory `/usr/src/CVS_DATA/opencxx/opencxx'
make: *** [all] Error 2


In my opinion it is the new std::auto_ptr which, afaik, has been modified.


BR

Vinzenz Feenstra

Re: [Opencxx-users] Preserve comments and layout

[Iwan B. <ib...@co...>]

I do not only want the comments to be preserved, but also: macros, =20
file/directory structure, includes etc. Actally everything, so the =20
transformed code would be equal to the base code if only a dummy =20
transformation is being made.

Regards,
Iwan
On Tue, 02 Nov 2004 19:20:19 +0800, Grzegorz Jakacki <ja...@ac...> =20
wrote:

>
>
> Stefan Seefeld wrote:
>>> From: Iwan Birrer [mailto:ib...@co...]
>>> Sent: November 1, 2004 12:06
>>
>>> Is it possible to transform C/C++ source code in a way that the layou=
t =20
>>> of
>>> the original source code is preserved? Or is it possble to parse and
>>> anylize code while the layout information is available is the AST.
>>   The layout of the original code is preserved. All changes you apply =
to
>> the parse tree are local and don't affect the code outside the scope
>> of the modified nodes.
>>  However, preprocessing is a separate stage that is delegated
>> from 'occ'
>
> occ2
>
>  > down to an external tool. I don't think comments are currently
>> preserved when the preprocessor is invoked that way. If you need this
>> you may want to preprocess the file yourself (using 'gcc -E -C' for
>> example) and then invoke 'occ' on the result.
>> But I could be wrong. Grzegorz ?
>
> Right modulo 'occ2'.
>
> BR
> Grzegorz
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=3D5588&alloc_id=3D12065&op=3Dclick
> _______________________________________________
> Opencxx-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opencxx-users



On Tue, 02 Nov 2004 19:20:19 +0800, Grzegorz Jakacki <ja...@ac...> =20
wrote:

>
>
> Stefan Seefeld wrote:
>>> From: Iwan Birrer [mailto:ib...@co...]
>>> Sent: November 1, 2004 12:06
>>
>>> Is it possible to transform C/C++ source code in a way that the layou=
t =20
>>> of
>>> the original source code is preserved? Or is it possble to parse and
>>> anylize code while the layout information is available is the AST.
>>   The layout of the original code is preserved. All changes you apply =
to
>> the parse tree are local and don't affect the code outside the scope
>> of the modified nodes.
>>  However, preprocessing is a separate stage that is delegated
>> from 'occ'
>
> occ2
>
>  > down to an external tool. I don't think comments are currently
>> preserved when the preprocessor is invoked that way. If you need this
>> you may want to preprocess the file yourself (using 'gcc -E -C' for
>> example) and then invoke 'occ' on the result.
>> But I could be wrong. Grzegorz ?
>
> Right modulo 'occ2'.
>
> BR
> Grzegorz
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=3D5588&alloc_id=3D12065&op=3Dclick
> _______________________________________________
> Opencxx-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opencxx-users

Re: [Opencxx-users] Porting OpenCXX

[<se...@in...>]

On Fri, 2004-11-05 at 08:05, Thomas Engelmeier wrote:
> Hi,
> 
> I currently wanted to evaluate OpenCXX for generation of language 
> bindings of crufty old C code into some reflectable languages on 
> MacOS X.
> 
> The 2.8 distribution has a bunch of problems:
> 
> - with the normal automake / autoconf / make chain there is a problem 
> that in most of the makefiles libtool is invoked, not something 
> configurable (glibtool on OS X) or the local libtool 
> ($OPENCXX/libtool).

Thomas thinks for your report.

>From the top_srcdir directory,
where the tarball has been decompressed
or checkout from cvs.

Executing the following command line
$ for i in `find -name Makefile.am`; do \
    echo "check in $i"; \
    grep libtool $i; \
  done

I have, the following output
check in ./Makefile.am
# use to automatically update the libtool script if it becomes
# out-of-date." [libtool.info]
libtool: $(LIBTOOL_DEPS)
check in ./buildinfo/Makefile.am
check in ./examples/before/Makefile.am
check in ./examples/matrix/Makefile.am
check in ./examples/runtime-mop/Makefile.am
check in ./examples/verbose/Makefile.am
check in ./examples/verbose2/Makefile.am
check in ./examples/wrapper/Makefile.am
check in ./examples/Makefile.am
check in ./html/Makefile.am
check in ./libltdl/Makefile.am
$(libltdl_la_OBJECTS) $(libltdlc_la_OBJECTS): libtool
libtool: $(LIBTOOL_DEPS)
        -rm -rf $(DESTDIR)$(datadir)/libtool/libltdl
        $(mkinstalldirs) $(DESTDIR)$(datadir)/libtool/libltdl
            cp -r $$d/$$file
$(DESTDIR)$(datadir)/libtool/libltdl/$$file; \
            test -f $(DESTDIR)$(datadir)/libtool/libltdl/$$file \
            || cp $$d/$$file $(DESTDIR)$(datadir)/libtool/libltdl/$$file
|| :; \check in ./opencxx/Makefile.am
check in ./scripts/Makefile.am
check in ./src/Makefile.am
# note, that we are using libtool, so it is libgc.la, not libgc.a
#     and libocc library; libocc is linked with libtool;
#     link the same object file with and without libtool;
#     for each source---for linking with and without libtool;
#     process, so that executable is obtained from libtool library.
# We want to make libtool library (.la)
check in ./testsuite/Makefile.am

This result let me beleive that the autoconf/automake tools
have not done their intended works.
the Makefile.in's and Makefile's file are generated files.

** i have absolutely no knowledge of MacOS X **, we can read from
http://developer.apple.com/documentation/Porting/Conceptual/PortingUnix/index.html?http://developer.apple.com/documentation/Porting/Conceptual/PortingUnix/revision_history/chapter_12_section_1.html
but this does not help us since it is the command line "libtool"
that is wrongly substituted in the Makefile.
That is, you what the command line "glibtool" instead for your system.

=====
check in ./libltdl/Makefile.am
in
http://developer.apple.com/documentation/DeveloperTools/glibtool/libtool_10.html
paragraph How to distribute libltdl with your package

   In order to embed libltdl into your package, just add `--ltdl'
   to the libtoolize command line. It will copy the libltdl sources
   to a subdirectory `libltdl' in your package. Both macros accept
   an optional argument to specify the location of the
   `libltdl' directory. By the default both macros assume
   that it is `${top_srcdir}/libltdl'.

You must read, the sources files provided in opencxx are not for
Mac OS X.  Used the already install "libltdl.so" from already
install package.

If you intend for testing purpose
or others reasons compile that library,
you must do
$ libtoolize --copy --automake --ltdl
before running './bootstrap' script from your top_scrdir of opencxx,
but I also expect that you know what you are doing.

That was to say,
step 1, ./bootstrap
step 2, ./configure ...
step 3, ./make ...
are the normal step.

During the make,
you will compile nothing in libltdl directory,
you will link nothing in libltdl directory.

hope this help
Gilles

> - compiled, one of the samples (IIRC verbose2) produces an coredump. 
> The problem is the sample tries to write to cout at static 
> initialisation time. The init order is _not_ guaranteed by the ANSI 
> Standard - while it is desirable std::cout is usuable all the time, 
> the only thing that is guaranteed is it is usuable when program 
> execution reaches the first line of main();
> 
> - With an more rigid ANSI compliant standard library implementation 
> (Metrowerks Codewarrior) there are compile errors due to missing 
> namespace using clauses in a whole bunch of files
> 
> ChangedMemberList.cc -> using std::memmove
> 
> Error   : undefined identifier 'strlen'
> auxil.cc line 28       int len = strlen(src);
> 
> Error   : undefined identifier 'strcpy'
> auxil.cc line 30       return strcpy(result, src);
> 
> etc...

I will recheck those one

> Regards,
> 	Tom_E

Re: [Opencxx-users] Porting OpenCXX

[Grzegorz J. <ja...@ac...>]

Thomas Engelmeier wrote:
> At 21:50 Uhr +0800 05.11.2004, Grzegorz Jakacki wrote:
> 
> Hi Grzegorz,
> 
>>> - with the normal automake / autoconf / make chain there is a problem 
>>> that in most of the makefiles libtool is invoked, not something 
>>> configurable (glibtool on OS X) or the local libtool ($OPENCXX/libtool).
>>
>>
>> You mean during building OpenC++ or compiling with OpenC++?
> 
> 
> Both. Most of the Makefiles refer to libtool even if $LIBTOOL is 
> defined, and the occ2 script does the same...
> 
>>> - compiled, one of the samples (IIRC verbose2) produces an coredump. 
>>> The problem is the sample tries to write to cout at static 
>>> initialisation time. The init order is _not_ guaranteed by the ANSI 
>>> Standard - while it is desirable std::cout is usuable all the time, 
>>> the only thing that is guaranteed is it is usuable when program 
>>> execution reaches the first line of main();
>>>
>>> - With an more rigid ANSI compliant standard library implementation 
>>> (Metrowerks Codewarrior) there are compile errors due to missing 
>>> namespace using clauses in a whole bunch of files
>>
>>
>> That's very valuable feedback. Could you send a patch agains 2.8 for 
>> these?
> 
> 
> If I figure out how to diff directories, yes ;-).

diff -r

> Whom should I send it to? (I'm not a fan of huge compiler error or 
> patchfile attachment on mailinglists)...

It's OK on this list.

BR
Grzegorz

Re: [Synopsis-devel] Re: [Opencxx-users] refining the Synopsis APIs

[Markus E. <Mar...@we...>]

> May be, if it was the only issue.

Well, the RGPL seems to be a good candidate. Does the boost license =
provide similar opportunities?

Would you like to use any Keystone components as base classes in =
Synopsis or OpenC++?

Regards,
Markus

Re: [Opencxx-users] Porting OpenCXX

[Thomas E. <te-...@en...>]

At 21:50 Uhr +0800 05.11.2004, Grzegorz Jakacki wrote:

Hi Grzegorz,

>>- with the normal automake / autoconf / make chain there is a 
>>problem that in most of the makefiles libtool is invoked, not 
>>something configurable (glibtool on OS X) or the local libtool 
>>($OPENCXX/libtool).
>
>You mean during building OpenC++ or compiling with OpenC++?

Both. Most of the Makefiles refer to libtool even if $LIBTOOL is 
defined, and the occ2 script does the same...

>>- compiled, one of the samples (IIRC verbose2) produces an 
>>coredump. The problem is the sample tries to write to cout at 
>>static initialisation time. The init order is _not_ guaranteed by 
>>the ANSI Standard - while it is desirable std::cout is usuable all 
>>the time, the only thing that is guaranteed is it is usuable when 
>>program execution reaches the first line of main();
>>
>>- With an more rigid ANSI compliant standard library implementation 
>>(Metrowerks Codewarrior) there are compile errors due to missing 
>>namespace using clauses in a whole bunch of files
>
>That's very valuable feedback. Could you send a patch agains 2.8 for these?

If I figure out how to diff directories, yes ;-).
Whom should I send it to? (I'm not a fan of huge compiler error or 
patchfile attachment on mailinglists)...

Regards,
	Tom_E

Re: [Opencxx-users] Porting OpenCXX

[Grzegorz J. <ja...@ac...>]

Thomas Engelmeier wrote:
> Hi,
> 
> I currently wanted to evaluate OpenCXX for generation of language 
> bindings of crufty old C code into some reflectable languages on MacOS X.
> 
> The 2.8 distribution has a bunch of problems:
> 
> - with the normal automake / autoconf / make chain there is a problem 
> that in most of the makefiles libtool is invoked, not something 
> configurable (glibtool on OS X) or the local libtool ($OPENCXX/libtool).

You mean during building OpenC++ or compiling with OpenC++?

> - compiled, one of the samples (IIRC verbose2) produces an coredump. The 
> problem is the sample tries to write to cout at static initialisation 
> time. The init order is _not_ guaranteed by the ANSI Standard - while it 
> is desirable std::cout is usuable all the time, the only thing that is 
> guaranteed is it is usuable when program execution reaches the first 
> line of main();
> 
> - With an more rigid ANSI compliant standard library implementation 
> (Metrowerks Codewarrior) there are compile errors due to missing 
> namespace using clauses in a whole bunch of files

That's very valuable feedback. Could you send a patch agains 2.8 for these?

Thanks!
Grzegorz

> 
> ChangedMemberList.cc -> using std::memmove
> 
> Error   : undefined identifier 'strlen'
> auxil.cc line 28       int len = strlen(src);
> 
> Error   : undefined identifier 'strcpy'
> auxil.cc line 30       return strcpy(result, src);
> 
> etc...
> 
> Regards,
>     Tom_E
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Opencxx-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opencxx-users

Re: [Opencxx-users] Getting OpenCXX to work under MSVC

[Grzegorz J. <ja...@ac...>]

Scott Shumaker wrote:
> Does anyone know the status on the work that has been done to get
> OpenCXX to work with MSVC?  We'd love to use it for the project we're
> working on, but Windows support is a must, and we unfortunately don't
> have much time to invest in configuration.

If you are concerned about parsing MSVC syntax, then some support for 
MSVC syntax is there, but I have never used it. As for compiling OpenC++ 
itself, 2.8 does not have makefiles for MSVC, but AFAIR Asen Kovachev 
was building it with MSVC, you may want to search archives and/or 
contact him.

BR
Grzegorz

[Opencxx-users] Porting OpenCXX

[Thomas E. <te-...@en...>]

Hi,

I currently wanted to evaluate OpenCXX for generation of language 
bindings of crufty old C code into some reflectable languages on 
MacOS X.

The 2.8 distribution has a bunch of problems:

- with the normal automake / autoconf / make chain there is a problem 
that in most of the makefiles libtool is invoked, not something 
configurable (glibtool on OS X) or the local libtool 
($OPENCXX/libtool).

- compiled, one of the samples (IIRC verbose2) produces an coredump. 
The problem is the sample tries to write to cout at static 
initialisation time. The init order is _not_ guaranteed by the ANSI 
Standard - while it is desirable std::cout is usuable all the time, 
the only thing that is guaranteed is it is usuable when program 
execution reaches the first line of main();

- With an more rigid ANSI compliant standard library implementation 
(Metrowerks Codewarrior) there are compile errors due to missing 
namespace using clauses in a whole bunch of files

ChangedMemberList.cc -> using std::memmove

Error   : undefined identifier 'strlen'
auxil.cc line 28       int len = strlen(src);

Error   : undefined identifier 'strcpy'
auxil.cc line 30       return strcpy(result, src);

etc...

Regards,
	Tom_E

RE: [Opencxx-users] Getting OpenCXX to work under MSVC

[Stefan S. <sse...@ar...>]

hi Scott,

> From: Scott Shumaker [mailto:ssh...@gm...]
> Sent: November 4, 2004 14:28

> As an aside, how scalable is OpenCXX?  Does anyone have experience
> using it with large-scale projects?

That depends on what you are referring to as 'OpenCXX'. If you are
talking about the occ (occ2) application, it's entirely file-based,
i.e. it doesn't much care about what project the file in question
is part of. In that sense it is as scalable as a compiler.

I can't answer your MSVC question as I'm currently not working
with the original OpenCxx code. I believe there are some potential
issues with the parser not understanding MSVC extensions 
(such as "throw(...)"). Also, I have no idea whether the build
system supports MSVC.

Regards,
		Stefan

[Opencxx-users] Getting OpenCXX to work under MSVC

[Scott S. <ssh...@gm...>]

Does anyone know the status on the work that has been done to get
OpenCXX to work with MSVC?  We'd love to use it for the project we're
working on, but Windows support is a must, and we unfortunately don't
have much time to invest in configuration.

Ironically, we will eventually be switching to a GCC-based environment
once the appropriate development hardware becomes available, but
that's probably quite a ways off.

As an aside, how scalable is OpenCXX?  Does anyone have experience
using it with large-scale projects?

Much thanks in advance.

Scott

Re: [Opencxx-users] Preserve comments and layout

[Grzegorz J. <ja...@ac...>]

Stefan Seefeld wrote:
>>From: Iwan Birrer [mailto:ib...@co...]
>>Sent: November 1, 2004 12:06
> 
> 
>>Is it possible to transform C/C++ source code in a way that 
>>the layout of
>>the original source code is preserved? Or is it possble to parse and
>>anylize code while the layout information is available is the AST.
> 
> 
> The layout of the original code is preserved. All changes you apply to
> the parse tree are local and don't affect the code outside the scope
> of the modified nodes.
> 
> However, preprocessing is a separate stage that is delegated
> from 'occ' 

occ2

 > down to an external tool. I don't think comments are currently
> preserved when the preprocessor is invoked that way. If you need this
> you may want to preprocess the file yourself (using 'gcc -E -C' for
> example) and then invoke 'occ' on the result.
> But I could be wrong. Grzegorz ?

Right modulo 'occ2'.

BR
Grzegorz

Re: [Opencxx-users] OpenC++ License

[Grzegorz J. <ja...@ac...>]

Markus Elfring wrote:
>>>1. The sentence specifies that this license variant must be repeated. 
>>
>> > Are there any legal reasons that allow to stop that repetition?
>>I don't think so anybody can do it without Xerox's aproval (relicensing).
> 
> Would you like to contact Xerox to discuss an eventual license change?

Yes, if this is necessary.

>>>3. How can license proliferation be resolved?
>>
>>I am looking for lawyer's help on these issues.
> 
> 
> Did you find anybody who would you like to participate in this topic?

Not yet, I am currently trying to solicit help from Berkman Center for 
Internet and Society at Harvard Law School.

BR
Grzegorz

RE: [Synopsis-devel] Re: [Opencxx-users] refining the Synopsis AP Is

[Stefan S. <sse...@ar...>]

> From: Markus Elfring [mailto:Mar...@we...]
> Sent: November 1, 2004 11:48

> Can this license issue be resolved if the Keystone project 
> would agree to use the "Runtime GPL"?
> http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/license.html
> 
> Can the discussion "(L)GPL and C++ templates issue" help here?
> http://groups.google.de/groups?group=comp.lang.c%2B%2B.moderat
> ed&threadm=4174046c%241_2%40news.bluewin.ch

May be, if it was the only issue.

Regards,
		Stefan

RE: [Opencxx-users] Preserve comments and layout

[Stefan S. <sse...@ar...>]

> From: Iwan Birrer [mailto:ib...@co...]
> Sent: November 1, 2004 12:06

> Is it possible to transform C/C++ source code in a way that 
> the layout of
> the original source code is preserved? Or is it possble to parse and
> anylize code while the layout information is available is the AST.

The layout of the original code is preserved. All changes you apply to
the parse tree are local and don't affect the code outside the scope
of the modified nodes.

However, preprocessing is a separate stage that is delegated
from 'occ' down to an external tool. I don't think comments are currently
preserved when the preprocessor is invoked that way. If you need this
you may want to preprocess the file yourself (using 'gcc -E -C' for
example) and then invoke 'occ' on the result.
But I could be wrong. Grzegorz ?

Regards,
		Stefan

RE: [Synopsis-devel] Re: [Opencxx-users] refining the Synopsis AP Is

[Markus E. <Mar...@we...>]

> * keystone is licensed under GPL, and thus not suitable for a 
>   framework that should be usable in proprietary settings, too.

Can this license issue be resolved if the Keystone project would agree to use the "Runtime GPL"?
http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/license.html

Can the discussion "(L)GPL and C++ templates issue" help here?
http://groups.google.de/groups?group=comp.lang.c%2B%2B.moderated&threadm=4174046c%241_2%40news.bluewin.ch

Regards,
Markus

[Opencxx-users] Preserve comments and layout

[Iwan B. <ib...@co...>]

Hello,

Is it possible to transform C/C++ source code in a way that the layout of
the original source code is preserved? Or is it possble to parse and
anylize code while the layout information is available is the AST.

Iwan

RE: [Synopsis-devel] Re: [Opencxx-users] refining the Synopsis AP Is

[Stefan S. <sse...@ar...>]

> From: Vladimir Prus [mailto:gh...@cs...]
> Sent: November 1, 2004 10:30

> On Monday 01 November 2004 17:44, Stefan Seefeld wrote:
> > > From: SF Markus Elfring [mailto:el...@us...]
> > > Sent: November 1, 2004 08:44
> > >
> > > I guess that you prefer the approach that is described by the
> > > papers on the page 
> "http://keystone.sourceforge.net/research.shtml".
> > > Would you like to reuse the software that was developed by
> > > the other project?
> >
> > You asked this question already in another thread. My answer
> > is still 'no'. For reasons see earlier discussions.
> 
> Stefan, do you have a pointer to that other thread? I'm not 
> saying we should 
> be using keystone, or parts of it (have no opinion), but is 
> interested what 
> you think.

Unfortunately it's hard to navigate through the archive of the
discussions, so let me restate my main points here:

* keystone is licensed under GPL, and thus not suitable for a 
  framework that should be usable in proprietary settings, too.

* keystone creates its syntax tree by copying the tokens from
  the input stream (the source code), while synopsis builds
  a parse tree as a structure *on top* of the underlaying buffer,
  i.e. keystone is lossy as far as low level information is concerned.

* as Gilles pointed out, keystone uses two SymbolTable structures,
  one part of the AST, the other part of the ASG. While that may
  be a sensible choice in the context of the keystone parser, I
  don't think that's required for synopsis.

Please note that I'm not familiar with keystone *in detail*, so take
the above with a grain of salt.

Regards,
		Stefan