[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

About revision 1407.... Again

To: soot-list@sable.mcgill.ca
Subject: About revision 1407.... Again
From: Venkatesh Prasad Ranganath <vranganath@cox.net>
Date: Tue, 09 Mar 2004 17:22:56 -0600
Sender: owner-soot-list@sable.mcgill.ca
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116

Hi,

In revision 1407, UnitGraph does not have a UnitGraph(Body,boolean,boolean) constructor!!! and this breaks my implementation :-(

I understand the copy in the repository is evolving. However, if such a change will make it's way into a subsequent release then I am wondering how does the Soot team decide on such API breaking changes? I am not against changes, but if it's a change affecting the published API then shouldn't the user base be informed or consulted before making such changes?

Can someone on the Soot team comment on the set of changes exposed in revision 1407? Is it wise to develop against these changes assuming that they will persist into the next release?

waiting for reply,

--

Venkatesh Prasad Ranganath,
Dept. Computing and Information Science,
Kansas State University, US.
web: http://www.cis.ksu.edu/~rvprasad

Follow-Ups:
- About revision 1407.... Again
  - From: John Jorgensen <jorgnsn@lcd.uregina.ca>

Prev by Date: About revision 1407
Next by Date: CFG and body dumping options (Was: About revision 1407)
Previous by thread: Re: is it wise to provide hooks to customizeExceptionalUnitGraph's constructors?
Next by thread: About revision 1407.... Again
Index(es):
- Date
- Thread