Re: [photran-dev] Refactoring the refactoring engine

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [photran-dev] Refactoring the refactoring engine

From: Jeffrey Overbey <subscribe-photran-dev@xxxxxxxxxxxx>
Date: Wed, 14 Oct 2009 15:26:00 -0500
Delivered-to: photran-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/photran-dev>
List-help: <mailto:photran-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/photran-dev>, <mailto:photran-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/photran-dev>, <mailto:photran-dev-request@eclipse.org?subject=unsubscribe>
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666

(1) the Refactoring class constructors will change, and

Oops. What I meant was, instead of passing an ArrayList<IFile> for theconstructors of SingleFileFortranRefactoring andMultipleFileFortranRefactoring, you will instead use a no-argumentconstructor, and then call #initialize(List<IFile>).


Jeff

References:
- [photran-dev] Refactoring the refactoring engine
  - From: Jeffrey Overbey

Prev by Date: [photran-dev] Refactoring the refactoring engine
Next by Date: RE: [photran-dev] Refactoring the refactoring engine
Previous by thread: [photran-dev] Refactoring the refactoring engine
Next by thread: RE: [photran-dev] Refactoring the refactoring engine
Index(es):
- Date
- Thread

Breadcrumbs