Re: obstinate syntax errors

2018-01-19 Thread Darryl Philip Baker
I don't have the time to put everything around this to do the syntax test but what happens with this: If ( ! chdir "/big/dom/x$server/data/students/$progress_hash{student_id}/" ) { $message = "Can't change directory to $progress_hash{student_id}: $!"; report_e

Re: obstinate syntax errors

2018-01-19 Thread Uri Guttman
On 01/19/2018 01:43 PM, Darryl Philip Baker wrote: I don't have the time to put everything around this to do the syntax test but what happens with this: If ( ! chdir "/big/dom/x$server/data/students/$progress_hash{student_id}/" ) { $message = "Can't change directory to $

Re: obstinate syntax errors

2018-01-19 Thread Rick T
Uri, Thank you SO much for your helpful comments! You didn’t just solve THIS problem, you’ve helped me in my future programming! Rick > On Jan 19, 2018, at 11:56 AM, Uri Guttman wrote: > > On 01/19/2018 12:44 PM, Rick T wrote: >> The subroutine below produces the followin

Re: obstinate syntax errors

2018-01-19 Thread Uri Guttman
On 01/19/2018 12:44 PM, Rick T wrote: The subroutine below produces the following syntax errors: syntax error at /big/dom/xexploringmyself/cgi-bin/register.cgi line 71, near ""Can't change directory to $progress_hash{student_id}: $!";" syntax error at /big/dom

obstinate syntax errors

2018-01-19 Thread Rick T
The subroutine below produces the following syntax errors: syntax error at /big/dom/xexploringmyself/cgi-bin/register.cgi line 71, near ""Can't change directory to $progress_hash{student_id}: $!";" syntax error at /big/dom/xexploringmyself/cgi-bin/register.cgi line

Re: Programmatically check for syntax errors without compiling the code

2011-03-30 Thread Michelle Konzack
Hello Magnus Woldrich, please can you send NON-ENCRYPTED messages please? Thanks, Greetings and nice Day/Evening Michelle Konzack -- # Debian GNU/Linux Consultant ## Development of Intranet and Embedded Systems with Debian GNU/Linux itsystems@tdne

Re: Programmatically check for syntax errors without compiling the code

2011-03-30 Thread Shawn H Corey
On 11-03-30 08:34 AM, Katie T wrote: "perl -c" will check your script without executing it. Not exactly. From `perldoc perlrun`: -c causes Perl to check the syntax of the program and then exit without executing it. Actually, it will execute "BEGIN", "UNITCHECK", "CHECK", and "use" blocks,

Re: Programmatically check for syntax errors without compiling the code

2011-03-30 Thread Katie T
On Tue, Mar 29, 2011 at 7:04 AM, Magnus Woldrich wrote: > > "perl -c" will check your script without executing it. Katie -- CoderStack http://www.coderstack.co.uk/asp-jobs The Software Developer Job Board

Re: Programmatically check for syntax errors without compiling the code

2011-03-29 Thread terry
2011-3-29 14:04, Magnus Woldrich: Can't see any message body but with two attachments. I'm using thunderbird 3. -- terry - te...@geekmail.de -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/

Programmatically check for syntax errors without compiling the code

2011-03-29 Thread Magnus Woldrich
binuRX8OPobbD.bin Description: application/pgp-encrypted msg.asc Description: Binary data

Re: Syntax Errors

2010-12-27 Thread Erez Schatz
On 12/27/2010 06:11 AM, Sisyphus wrote: > > - Original Message - From: "Randal L. Schwartz" > > To: > Sent: Monday, December 27, 2010 1:57 PM > Subject: Re: Syntax Errors > > >>>>>>> "Bill" == Bill Casey

Re: Syntax Errors

2010-12-26 Thread Sisyphus
- Original Message - From: "Randal L. Schwartz" To: Sent: Monday, December 27, 2010 1:57 PM Subject: Re: Syntax Errors "Bill" == Bill Casey writes: Bill> Syntax error at import_track.pl line 11, near ") {" Bill> Syntax error at import_trac

Re: Syntax Errors

2010-12-26 Thread Randal L. Schwartz
>>>>> "Sheppy" == Sheppy R writes: Sheppy> Strawberry Perl under Padre on a Windows system will give Syntax errors Sheppy> (Running from both the command-line and in Padre itself). Chances are this Sheppy> is where Bill is getting them from, probably just one

Re: Syntax Errors

2010-12-26 Thread Sheppy R
Strawberry Perl under Padre on a Windows system will give Syntax errors (Running from both the command-line and in Padre itself). Chances are this is where Bill is getting them from, probably just one of the differences between *nix and Windows. @Bill - I'm not seeing any problems when I

Re: Syntax Errors

2010-12-26 Thread Randal L. Schwartz
> "Bill" == Bill Casey writes: Bill> Syntax error at import_track.pl line 11, near ") {" Bill> Syntax error at import_track.pl line 14, near "}" Perl doesn't ever say "syntax error". So those errors are not coming from Perl. First thing to figure out is why Perl isn't running your script

Re: Syntax Errors

2010-12-19 Thread Shlomi Fish
On Sunday 19 December 2010 22:23:15 Bill Casey wrote: > Hi > > Below is a Perl script which won't compile. My operating system is > Windows XP Home and Perl version is 5.10.1.3. > This script after I placed it in a file compiles fine here: {{{ shlomif:~$ cat test.pl #!/usr/bin/perl # import_tr

Syntax Errors

2010-12-19 Thread Bill Casey
Hi Below is a Perl script which won't compile. My operating system is Windows XP Home and Perl version is 5.10.1.3. #!/usr/bin/perl # import_track.prl use warnings; use strict; open (INFILE, "track.txt") or die $!; open (OUTFILE, ">outtrack.plt") or die $!; my $outstring; while () {

Re: syntax errors?

2006-03-29 Thread Tom Phoenix
On 3/28/06, Mr. Shawn H. Corey <[EMAIL PROTECTED]> wrote: > On Tue, 2006-28-03 at 17:42 -0800, Christopher Spears wrote: > > my $sum{$source} += my > > $total_bytes{$source}{$destination}; > > The second 'my' is causing the error. What does the first one cause? --Tom Phoenix Stonehenge Perl T

Re: syntax errors?

2006-03-28 Thread Mr. Shawn H. Corey
On Tue, 2006-28-03 at 17:42 -0800, Christopher Spears wrote: > my $sum{$source} += my > $total_bytes{$source}{$destination}; The second 'my' is causing the error. -- __END__ Just my 0.0002 million dollars worth, --- Shawn "For the things we have to learn before we can do them, we l

Re: syntax errors?

2006-03-28 Thread Tom Phoenix
On 3/28/06, Christopher Spears <[EMAIL PROTECTED]> wrote: > my $sum{$source} += my > $total_bytes{$source}{$destination}; > Am I missing something? My guess is that my declarations have infested my program. Err, your program. You can only use my() with complete variables, not with elements

syntax errors?

2006-03-28 Thread Christopher Spears
I'm trying to solve a problem in Intermediate Perl. Basically, I open a text file and read its information. Here is some text from the file: gilligan.crew.hut lovey.howell.hut 4721 thurston.howell.hut lovey.howell.hut 4046 professor.hut ginger.girl.hut 5768 gilligan.crew.hut laser3.copyroom.hut

Re: finding syntax errors

2003-10-27 Thread Motherofperls
I use editpadpro, (there is a lite free version of it). You can download syntax color schemes for perl code. It will give you the matching brace or parenthesis. http://www.editpadpro.com/cscs.html

Re: finding syntax errors

2003-10-26 Thread Kevin Pfeiffer
In article <[EMAIL PROTECTED]>, Kevin Pfeiffer wrote: > I've painted myself into a corner I can't get out of... > > Missing right curly or square bracket at /home/pfeiffer/bin/trash line > 341, at end of line > syntax error at /home/pfeiffer/bin/trash line 341, at EOF > Execution of /home/pfeiffe

finding syntax errors

2003-10-26 Thread Kevin Pfeiffer
I've painted myself into a corner I can't get out of... Missing right curly or square bracket at /home/pfeiffer/bin/trash line 341, at end of line syntax error at /home/pfeiffer/bin/trash line 341, at EOF Execution of /home/pfeiffer/bin/trash aborted due to compilation errors. Line 341 is, of cou

RE: why am I getting syntax errors ?

2002-01-08 Thread Peter Cornelius
This sort of question is a lot easier if we could see the syntax errors. Here's my guess though. #foreach $i (@section_headers) Has $i been declared? Try 'foreach my $i (@section_headers)' #die "config error - no valid section header\n" if ($config_current_s

Re: why am I getting syntax errors ?

2002-01-08 Thread Matt C.
ection ." \n", > #foreach $i (@section_headers) > # { > # $config_current_section = (lc($config_section) eq $i) ? > $i:$config_current_section > # }, > #die "config error - no valid section header\n" if > ($config_current_section ne $co

why am I getting syntax errors ?

2002-01-08 Thread Filip Sneppe
n # }, #die "config error - no valid section header\n" if ($config_current_section ne $config_section && $config_current_section ne "queries"), # for(my $x;$x<10;++$x) print "gg", print "in section $config_current_section -> $config