<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16544" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=802492806-22112007><FONT face="Courier New"
size=2>Hi,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=802492806-22112007><FONT face="Courier New"
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=802492806-22112007><FONT face="Courier New"
size=2>Not sure what you're asking about commented IDL, but it
has</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=802492806-22112007><FONT face="Courier New"
size=2>always been ignored.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=802492806-22112007><FONT face="Courier New"
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=802492806-22112007><FONT face="Courier New"
size=2>Jeff</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Vikram Karandikar
[mailto:softking@gmail.com] <BR><B>Sent:</B> Wednesday, November 21, 2007
11:45 PM<BR><B>To:</B> Doug Schmidt<BR><B>Cc:</B> Jeff Parsons;
tao-users@cse.wustl.edu<BR><B>Subject:</B> Re: [tao-users] Making use of TAO
IDL compiler<BR></FONT><BR></DIV>
<DIV></DIV>Hi,<BR><BR>thanks to all of you.<BR>i will surely consider your
suggestions.<BR>for the time being i will try to modify the current tao_idl
compiler code to generate constructors (keeping in mind the points given by
Johnny & J.T. Conklin).<BR>One more thing i would like to ask, the
parser (SunSoft) will not add commented code in the IDL file as a node in the
AST.<BR>So is there anyway to tell parser that do include the comments in the
IDL file as the nodes in the AST. <BR>If yes after doing this will the normal
(means the current and not the one which i have modified) tao_idl ignore these
comments?<BR><BR>
<DIV class=gmail_quote>On Nov 22, 2007 12:20 AM, Douglas C. Schmidt <<A
href="mailto:schmidt@dre.vanderbilt.edu"> schmidt@dre.vanderbilt.edu</A>>
wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><BR>Hi
Folks,<BR>
<DIV class=Ih2E3d><BR>> The linked paper is on the use of patterns to
implement <BR>> AMI in TAO. I skimmed the paper quickly - if there
are<BR>> any references to the IDL compiler in it, they are not<BR>>
very significant ;-).<BR><BR></DIV>Sorry, I was "off-by-one" - please
see<BR><BR><A href="http://www.cs.wustl.edu/%7Eschmidt/PDF/ami1.pdf"
target=_blank>http://www.cs.wustl.edu/~schmidt/PDF/ami1.pdf</A><BR><BR>for
the article that discusses hw the TAO IDL compiler backend can
be<BR>extended to generate different sorts of stuff.
<BR><BR>Thanks,<BR><BR>Doug<BR>
<DIV>
<DIV></DIV>
<DIV class=Wj3C7c><BR>> Jeff<BR>><BR>> > -----Original
Message-----<BR>> > From: <A
href="mailto:schmidt@dre.vanderbilt.edu">schmidt@dre.vanderbilt.edu</A>
[mailto:<A
href="mailto:schmidt@dre.vanderbilt.edu">schmidt@dre.vanderbilt.edu</A>]<BR>>
> Sent: Wednesday, November 21, 2007 10:14 AM<BR>> > To: <A
href="mailto:jtc@acorntoolworks.com">jtc@acorntoolworks.com </A>; Jeff
Parsons<BR>> > Cc: <A
href="mailto:tao-users@cse.wustl.edu">tao-users@cse.wustl.edu</A><BR>>
> Subject: Re: [tao-users] Making use of TAO IDL compiler<BR>>
><BR>> > Hi Folks,<BR>> > <BR>> > There is a paper we
wrote about the patterns used in the TAO<BR>> > IDL compiler to
support multiple backend pluggins. The<BR>> > patterns include
Visitor, Abstract Factory, and Strategy. I<BR>> > think the paper is
available at <BR>> ><BR>> > <A
href="http://www.cs.wustl.edu/%7Eschmidt/PDF/ami2.pdf"
target=_blank>www.cs.wustl.edu/~schmidt/PDF/ami2.pdf</A><BR>>
><BR>> > If this isn't the right paper I will find the right one
when <BR>> > I am done with holiday travels today!<BR>>
><BR>> > Thanks,<BR>> ><BR>> > Doug<BR>> > Sent
from my BlackBerry(r) wireless device<BR>> ><BR>> >
-----Original Message----- <BR>> > From: <A
href="mailto:jtc@acorntoolworks.com">jtc@acorntoolworks.com</A> (J.T.
Conklin)<BR>> ><BR>> > Date: Wed, 21 Nov 2007 08:02:50<BR>>
> To:"Jeff Parsons" <<A href="mailto:j.parsons@vanderbilt.edu">
j.parsons@vanderbilt.edu</A>><BR>> > <A
href="mailto:Cc:tao-users@cse.wustl.edu">Cc:tao-users@cse.wustl.edu</A><BR>>
> Subject: Re: [tao-users] Making use of TAO IDL compiler<BR>>
><BR>> ><BR>> > "Jeff Parsons" < <A
href="mailto:j.parsons@vanderbilt.edu">j.parsons@vanderbilt.edu</A>>
writes:<BR>> > > Maybe I'm misunderstanding what you mean by
'pluggable<BR>> > > back end support' for the TAO IDL compiler, but
there <BR>> > > are already several backend generator libraries
used<BR>> > > with the same frontend parser library and driver
executable.<BR>> > > In the TAO distribution, please see<BR>>
> > TAO_ROOT/orbsvcs/IFR_Service where, in addition to the IFR
<BR>> > > Service executable, there are files to build an IFR
loader<BR>> > > backend for the IDL compiler. In the CIAO
distribution,<BR>> > > there is a backend in
CIAO_ROOT/tools/IDL3_to_IDL2 that <BR>> > > converts IDL containing
component and home declarations<BR>> > > into the equivalent
'implied IDL'. Other backends can<BR>> > > be found in the CoSMIC
toolsuite distribution that convert <BR>> > > IDL into PICML, our
component system modeling language,<BR>> > > and WSDL (Web Services
Definition Language).<BR>> ><BR>> > Hi Jeff,<BR>>
><BR>> > While I was aware that the IDL compiler and IFR used the
same front <BR>> > end with different back end libraries, I wasn't
aware that there were<BR>> > so many other back ends. Also I'm looking
at the current sources, and<BR>> > I'm not seeing the use of the
tao_idl driver executable; it appears <BR>> > tao_ifr links the
driver, front end, and back end libraries together.<BR>> > And the
TAO_IFR_Loader appears to be service config object (to be used<BR>> >
with TAO_Service, etc.), which is the dynamically loaded equivalent of
<BR>> > the IFR_Service server. To the best I can tell, it
doesn't act on IDL<BR>> > (The IFR_Server library isn't linked with
any of the TAO_IDL<BR>> > libraries).<BR>> ><BR>> >
However, the multiple back ends suggests that TAO's IDL compiler may
<BR>> > be much farther along towards what I was meaning by
"pluggins".<BR>> ><BR>> > It's my understanding that the OmniORB
IDL compiler you can specify a<BR>> > back end on the command line,
and that back end will be used when <BR>> > compiling the IDL.
The OmniORB back ends are written in python, which<BR>> > makes
things a bit easier. I vaguely recall reading docs for one of<BR>>
> the commercial ORBs (Orbix?) that had a similar capability where the
<BR>> > plugins were writtin in something like tcl.<BR>>
><BR>> > For TAO, I was imagining the backend interface being a
dynamically<BR>> > loaded library loaded by the driver. A
somewhat higher barrier to <BR>> > entry than python or tcl, but still
very usable.<BR>> ><BR>> > --jtc<BR>>
><BR>> > --<BR>> > J.T. Conklin<BR>> ><BR>> >
_______________________________________________ <BR>> > tao-users
mailing list<BR>> > <A
href="mailto:tao-users@mail.cse.wustl.edu">tao-users@mail.cse.wustl.edu</A><BR>>
> <A href="http://mail.cse.wustl.edu/mailman/listinfo/tao-users"
target=_blank>http://mail.cse.wustl.edu/mailman/listinfo/tao-users</A><BR>>
><BR><BR>_______________________________________________<BR>tao-users
mailing list<BR><A
href="mailto:tao-users@mail.cse.wustl.edu">tao-users@mail.cse.wustl.edu
</A><BR><A href="http://mail.cse.wustl.edu/mailman/listinfo/tao-users"
target=_blank>http://mail.cse.wustl.edu/mailman/listinfo/tao-users</A><BR></DIV></DIV></BLOCKQUOTE></DIV><BR><BR
clear=all><BR>-- <BR>"There is no substitute for intelligence, experience,
common sense, and good taste." - Bjarne Stroustrup <BR><BR>- Vikram Karandikar
</BLOCKQUOTE></BODY></HTML>