[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [Dltk-dev] 'validator core' vs 'external checker'
|
Hi Jae,
ExternalChecker is a standalone implementation for generic cases, your implementation should depend on validators.core plugin.
At the moment DLTK contains 2 validator implementations: external checker and tclchecker. The main difference is the output processing. Command line is constructed differently too, but it is not a big deal.
I am working with tclchecker now, and it looks like we can extract some common code to the validators.core.
Regards,
Alex
----- Original Message -----
From: "Jae Gangemi" <jgangemi@xxxxxxxxx>
To: "DLTK Developer Discussions" <dltk-dev@xxxxxxxxxxx>
Sent: Sunday, October 26, 2008 4:51:12 AM GMT +06:00 Almaty, Novosibirsk
Subject: [Dltk-dev] 'validator core' vs 'external checker'
hello all -
i'm working on adding 'perl -c' support using the IValidator interfaces provided by the validator core. i looked at using the 'external checker', however that doesn't suit all of my needs - although it does have a lot of good functionality in it that i want to leverage.
my question is, where should some of that common code live? should i be depending on the 'external checker' plugin, or is that intended more to be a stand alone implementation for generic validator support and my only validator dependency should be against the 'core'?
--
-jae
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev
