Re: warnings or -w ?

In article <Xns9872A8BAC82DFasu1cornelledu@xxxxxxxxx>,
1usa@xxxxxxxxxxxxxxxxxxx says...
Not necessary to be agressive unless you spent a bad day :)

He wasn't being agressive, just giving good advice.


Not sure... In this thread Sisyphus and you gave me good advice (see
below) !

I am assuming you are FTP'in these scripts to the FC5 server from a
Windows computer. In that case, make sure they are transferred in ASCII
mode.


In fact, no : my own stations are one under Windows and the second under
Ubuntu ; however, it's a fact I generally write a first release under
Win, then transfert to Ubuntu for testing and final upload toward
servers. And, in rare case, I ftp upload from Win, ascii mode is well
asociated with .pl extension.

Your problem very likely has absolutely nothing to do with the warnings
module, but with the presence of options on the shebang line. For
example, I am guessing that

#!/usr/bin/perl --


You're absolutely right here ! So, I've searched what could be wrong in
the "scripts with problem"... Well, the fact is that, here, every
developer send his work to all other developers for final check and (it
was difficult to figure out)... And the Linux servers on which problem
occured were, all, managed or co-managed by a single man who recently
installed a different Komodo release for his own usage. The problem is
that in these Komodo settings, he (surely not volontarily because it has
not any sense) checked "preserve existing line ending" as "\r\n". So,
even if file were correctly ftp uploaded (with line ending conversion),
this simple checkbox does every scripts which have been re-edited
locally in these Komodo has been changed back with Win style \r\n.

Fortunately this has no influence on final end-user servers because,
after checking and approval of all developers (who report their opinion
back to original developper), the scripts which are finally released are
the one (modified or not) from original plateform.

I've changed by myself this Komodo settings on the FC5 server and
propagated the things toward team for local checking. Solved ! Thanks
.

Relevant Pages

  • Re: Eggs, VirtualEnv, and Apt - best practices?
    ... And while our servers use Linux (and I as developer as ... all the rest of our people use windows. ... environment: Debian/Ubuntu so my post was relative to the original request. ... But then it's better when your developers develop on ...
    (comp.lang.python)
  • Re: What is your Game Of The Decade pick?
    ... released you cant fault the developers commitment to the title. ... confusion with different servers requiring different things to join. ... System Shock 2, probably because I never could get it to run on an XP system ... Bioshock, similar reason, trying to hype it as a spirital succesor to SS2 ...
    (comp.sys.ibm.pc.games.action)
  • Re: VS 2005 questions
    ... can't use VS 2005 for a few years, but at least our developers can prepare ... because the applications must be hosted on military servers over which we ... Microsoft software is among the most mission-critical for them, ... because then developers could adopt VS 2005 more quickly. ...
    (microsoft.public.vsnet.general)
  • Re: Quality of FreeBSD
    ... >> I know the developers don't hear it often enough, ... Mainly NFS and Samba servers, ... Some special kind words go to Soren Schmidt here. ...
    (freebsd-stable)
  • Re: Windows 2000 - Read only access for developers.
    ... In the internal domain developers can already see the Event Viewer and COM+ ... need to see would typically have access denied from say the guest account. ... servers in order to effect this. ...
    (microsoft.public.win2000.general)