[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [imp-dev] IParseController.parse() parameter 'scanOnly'
|
Hi
Certainly seems sensible; I couldn't figure out how to code
an implementation that used the parameter given that the
callers did not appear coherent and given that
https://bugs.eclipse.org/bugs/show_bug.cgi?id=257627
identifies that parser synchronisation is currently badly broken.
Maybe once designed the new interface may use an IParseSynchronizer??
Regards
Ed Willink
> -----Original Message-----
> From: imp-dev-bounces@xxxxxxxxxxx
> [mailto:imp-dev-bounces@xxxxxxxxxxx] On Behalf Of Robert M. Fuhrer
> Sent: 12 March 2009 14:52
> To: IMP Developers List
> Cc: Jurgen Vinju; Philippe G. Charles
> Subject: [imp-dev] IParseController.parse() parameter 'scanOnly'
>
>
> Hi All,
>
> I'd like to remove this formal parameter from the interface. Its
> original intent
> was to permit a quick re-scan of the source without a full
> parse, but
> the
> problem of scheduling analyses for responsiveness is much deeper than
> this one flag addresses (and arguably incremental
> scanning/parsing is a
> superior solution). Oh, and no one is actually using it (that I'm
> aware of). :-)
>
> Any objections?
>
> --
> Cheers,
> - Bob
> -------------------------------------------------
> Robert M. Fuhrer
> Research Staff Member
> Programming Technologies Dept.
> IBM T.J. Watson Research Center
>
> IMP Project Lead (http://www.eclipse.org/imp)
> X10: Productivity for High-Performance Parallel Programming
> (http://x10.sf.net
> )
>
> _______________________________________________
> imp-dev mailing list
> imp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/imp-dev
>
