Hi all,
Thanks for the interest in the problem and in the language.

First, regarding to CPD tokenizer requirement - looking inside CPD sources I see they need the yokenized data in java structure. heir own PHP and C++ tokenizers are written in Java, but it doe snot mean we cannot execute Perl tokenizer, and they import the data (though it will take time to fit the information, I guess).

Meanwhile I executed CPD over some C code and got very nice results. When changing my Perl files into .java I got some limited answers as well, so I might just use what I got. It depends whether I will get the reources (tiem and people) to work on it or not.

Regarding to the language, and the primary language -

It is called QTL, and it comes for Qa Testing Language

Using this language we were able to execute distributed tests over any number of machines in a multi platform environment. All, BTW, written in Perl.

The new version, already working for a year, reduced the amount of special QTL commands, and gave the developer (almost) full Perl capabiliites.

Two main objects are use in QTL/Perl - a machine, and a label

$machine->command() will execute the command on the remote machine, and will return a $label.

$label->attribute (such as result, state, exitcode) will check the executed command and give the developer updated status all of the time

The converter from the old language to the new syntax was rather simple, and was executed a year ago. This means we cannot go back to the old sources, since we had many changes already.

I cannot give more information without management approval (which I won't get, I believe) - this is not an open source project. On the other hand, I plan to give a lecture in YAPC::Israel::2004 which will take place on February 2004, so you are all welcome.

Back to our business - the duplication detector - although it is very interesting stuff, unless I come up with a fully automatic tool that find duplications over several files and give the user proper information on what to do with them, I believe I will need to take some of your advices, and work manually on it.

Question is - what do you think will take longer, and what do you think will be more reliable ?

Thanks,
shushu

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

Outside of code tags, you may need to use entities for some characters:

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.