From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,4c459ff0adb576bc X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-02-10 06:18:20 PST From: "Martin Dowie" Newsgroups: comp.lang.ada References: <3C5AB0B7.9D75D49A@grammatech.com> <3c639940@pull.gecm.com> <4519e058.0202080714.1bf916bb@posting.google.com> <4Wh98.39579$L02.1707804819@newssvr30.news.prodigy.com> Subject: Re: Re: Refactoring and Ada Date: Sun, 10 Feb 2002 13:57:36 -0000 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 NNTP-Posting-Host: ed125012.sd.edinbr.gmav.gecm.com Message-ID: <3c667c4a$1@pull.gecm.com> X-Trace: 10 Feb 2002 13:57:30 GMT, ed125012.sd.edinbr.gmav.gecm.com Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!cpk-news-hub1.bbnplanet.com!news.gtei.net!nntp.abs.net!feeder.qis.net!btnet-peer!btnet-peer0!btnet-feed5!btnet!newreader.ukcore.bt.net!pull.gecm.com!ed125012.sd.edinbr.gmav.gecm.com Xref: archiver1.google.com comp.lang.ada:19832 Date: 2002-02-10T13:57:36+00:00 List-Id: > > Yeah - with an option for 'native' or 'ravenscar' :-) > > Nice idea! > > > I have been toying with the scripts to try and cope with transforming C++ > > names that are invalid in Ada into something that would be ok - then I could > > import C++ code into UML classes and produce Ada from those. Do > > you have any info. on the scripting language used? I'm flying blind here! > > It's a close cousin to Lisp. I already have a function in there that makes Ada > names (converting interior blanks into underscores, etc.) from the diagram > elements, perhaps that would be the place to start. But it doesn't look for > leading underscores, a la C++. Look for a function named 'MakeAdaName'. Thanks, yes, that's exactly where I've been playing about. As well as leading underscores, there are trailing underscores to consider and also 'what do you change it to?' I doubt just removing either underscore would be good enough as (bizarrely) there may be another field with that name! A known and _very_ random pre/post fix could be added I suppose... not 100% bullet proof but with suitable 'information text' the user could decide what to do