6.1 The QA team would not have to rush to the devlopers each time there is some problem or some enhacement.They know perl better.

6.2 Perl is widely known two be very good is string comparison.

6.3 I have been told by my Lead)(i have to make it and make it good else i would be kicked out :-))

Hmmm ....

I suddenly have that magic bullet feeling

From what I've read of your problem, there may be a number of approaches.

My limited experience of C++ is that it can lead to a lot of bloat. However such code can be trimmed down to be near C-like in performance and size. I think, but I can't be sure, that this is due to the way the code is written and the way the code is built.

So has the C++ group bothered to review and trim that code?

The concept that you have been given this task just because there's a rumour that Perl is good at string comparison - without any analysis of how Perl might help being commissioned first, indicates a lack of planning somewhere in your group structure.

A manager threatening someone with loss of employment on the basis of both poor planning and exploring whether a rumour is true?

Well, these days, if I were in permanent employment, having verified what planning or assessment of the problem had taken place - and seen the supporting documentation and code to validate chasing this rumour - which in this case I'm guessing doesn't exist - my response to this threat would be to discuss the term 'constructive dismissal' with the individual concerned.

While one might elect to pursue that matter further, or might not, it may be an effective warning shot to prevent that individual putting you way out on a limb and then sawing it off at the trunk end again.

In reply to Re^17: Problem in Inter Process Communication by LesleyB
in thread Problem in Inter Process Communication by libvenus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &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.