Hey, I'm trying to make an interactive perl program and while I'm not done I wanted to share the bit of code I have at the moment because I keep running into an error that says that it "Found = in conditional, should be ==" in my code. This is my code-
Code:
use warnings;
use strict;
my $i;
$i=0;
while ($i=0)
{
print "Welcome to an interactive Perl program. Enter either q or Q to terminate the program or c to continue. Enter your key now: ";
my $input;
$input = <STDIN>;
if (($input ne "q") || ($input ne "Q") || ($input ne "c"))
{
print "Welcome to an interactive Perl program. Enter either q or Q to terminate the program or c to continue. Enter your key now: ";
}
elsif (($input eq "q") || ($input eq "Q"))
{
exit;
}
else
{
print "Please enter one x coordinate: ";
my $x1;
$x1 = <STDIN>;
print "Please enter one y coordinate: ";
my $y1;
$y1 = <STDIN>;
print "Please enter one z coordinate: ";
my $z1;
$z1 = <STDIN>;
print "Please enter a second x coordinate: ";
my $x2;
$x2 = <STDIN>;
print "Please enter a second y coordinate: ";
my $y2;
$y2 = <STDIN>;
print "Please enter a second z coordinate: ";
my $z2;
$z2 = <STDIN>;
}
}
The line the error specifies is the line with just "{" under the line with the while keyword. Can anyone help?
To give more specifics on the code, I'm inviting the user to the program and asking them to hit 'q' or 'Q' to terminate it or 'c' to continue it. If they don't hit either of those three keys, I want the program to keep prompting the user to enter either 'q' or 'Q' or 'c'. If they hit 'q' or 'Q' then I want the program to be terminated. If they hit c the code then starts to do one of the main functions for this program, which is to take two three dimensional coordinates from the user and find the distance between them, but I still haven't completed this part yet. At the moment I just want to know what the error could be referring to and how to fix it. And if there's anything wrong with my code, please let me know.
Hi I have to move data to a file based on the valuies of first three characters in a file I am using the following script
FIN=$LOC/TEST.TXT
FEEDFILE=$LOC/TUE_GROSSJE.TXT
#Read the file
while read FDROW
do
FEEDROW=$FDROW;
DTYPE=`echo $FEEDROW |cut -c 1-3`
if ; then
$FEEDROW... (4 Replies)
Hi ,
Please answer my query:
I want to create a common make file for one of mylibrary such that it should work on both Sun as well as Linux on 32 and 64 bit system.
The flow is sth like this:
..............
..............
if$(OS) == solaris
BINDIR= ../../lib/solaris/64
else
BINDIR=... (1 Reply)
Hello everyone,
I am using Linux and tcsh shell. I am trying to run a free open source program( which is in the form of a binary file), but every time I run it it gives me an error saying:
newhtsg_v1.0:Command not found.
I have set permission also for the same.
What else can I do to make... (4 Replies)
Hi Friends,
I am using valgrind, to check errors, there are no errors in my code but this the output put i get, i need to suppress these errors, please help me do so...
Conditional jump or move depends on uninitialised value(s)
==2350== at 0x400AF0F: (within /lib/ld-2.11.1.so)... (0 Replies)
I have a program called abc installed in /usr/local/bin.
My path is as follows:
# echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin
However, when entering the abc command, the following error appears:
# abc
abc: Command not found
When... (7 Replies)
Hi, I get a "FILEPATH: not found" error on the 3rd line and the line where it is within the case. Any idea as to why I'm getting this error time and time again?
Oh and FILEPATH will store the directory of the file.
I appreciate any help!
IAM=`basename $0`
RC=0
FILEPATH = ""... (1 Reply)
Hello All,
I am running source command on my project configuration file app.cfg which has conditional statements with make file systax E.g ifeq ($(APP_CMP_DIR),trunk).
When I source this file it throws error: syntax error near unexpected token... (1 Reply)
$ cat nu
who | wc -l
$ ls -l nu
-rwxr-x--- 1 _ _ 11 Jul 30 12:37 nu //the nu is displayed in green color
$ nu
bash: nu: command not found
I am using a book from 1986 on Unix System V, Release 3, and the Unix system I am connecting to is from my college.
Below is the notes from the book:... (4 Replies)
Hi experts,
I am doing an exercise which has the following requirements.
Charlie will bite your finger exactly 50% of the time. First, write a function isBitten() that returns TRUE with 50% probability, and FALSE otherwise
To generate a webpage that displays "Charlie bit your finger!" or... (1 Reply)
Hi,
Below is my code where i m trying to grep for name>$servername in manages*.tmp files
servername="serv1"
set manages*.tmp
if ; then
However, i get the below error at the if condition:
Can you please suggest how can i fix the problem. (3 Replies)
Discussion started by: mohtashims
3 Replies
LEARN ABOUT DEBIAN
ptksh
PTKSH(1p) perl/Tk Documentation PTKSH(1p)NAME
ptksh - Perl/Tk script to provide a graphical user interface for testing Perl/Tk commands and scripts.
SYNOPSIS
% ptksh ?scriptfile?
... version information ...
ptksh> $b=$mw->Button(-text=>'Hi',-command=>sub{print 'Hi'})
ptksh> $b->pack
ptksh> o $b
... list of options ...
ptksh> help
... help information ...
ptksh> exit
%
DESCRIPTION
ptksh is a perl/Tk shell to enter perl commands interactively. When one starts ptksh a MainWindow is automaticly created, along with a
ptksh command window. One can access the main window by typing commands using the variable $mw at the 'ptksh> ' prompt of the command
window.
ptksh supports command line editing and history. Just type "<Up>" at the command prompt to see a history list. The last 50 commands
entered are saved, then reloaded into history list the next time you start ptksh.
ptksh supports some convenient commands for inspecting Tk widgets. See below.
To exit ptksh use: "exit".
ptksh is *not* a full symbolic debugger. To debug perl/Tk programs at a low level use the more powerful perl debugger. (Just enter ``O
tk'' on debuggers command line to start the Tk eventloop.)
FEATURES
History
Press <Up> (the Up Arrow) in the perlwish window to obtain a gui-based history list. Press <Enter> on any history line to enter it into
the perlwish window. Then hit return. So, for example, repeat last command is <Up><Enter><Enter>. You can quit the history window with
<Escape>. NOTE: history is only saved if exit is "graceful" (i.e. by the "exit" command from the console or by quitting all main
windows--NOT by interrupt).
Debugging Support
ptksh provides some convenience function to make browsing in perl/Tk widget easier:
?, or h
displays a short help summary.
d, or x ?args, ...?
Dumps recursively arguments to stdout. (see Data::Dumper). You must have <Data::Dumper> installed to support this feature.
x was introduced for perl debugger compatibility.
p ?arg, ...?
appends "|
" to each of it's arguments and prints it. If value is undef, '(undef)' is printed to stdout.
o $widget ?-option ...?
prints the option(s) of $widget one on each line. If no options are given all options of the widget are listed. See Tk::options for
more details on the format and contents of the returned list.
o $widget /regexp/
Lists options of $widget matching the regular expression regexp.
u ?class?
If no argument is given it lists the modules loaded by the commands you executed or since the last time you called "u".
If argument is the empty string lists all modules that are loaded by ptksh.
If argument is a string, ``text'' it tries to do a ``use Tk::Text;''.
Packages
Ptksh compiles into package Tk::ptksh. Your code is eval'ed into package main. The coolness of this is that your eval code should not
interfere with ptksh itself.
Multiline Commands
ptksh will accept multiline commands. Simply put a "" character immediately before the newline, and ptksh will continue your command onto
the next line.
Source File Support
If you have a perl/Tk script that you want to do debugging on, try running the command
ptksh> do 'myscript';
-- or (at shell command prompt) --
% ptksh myscript
Then use the perl/Tk commands to try out different operations on your script.
ENVIRONMENT
Looks for your .ptksh_history in the directory specified by the $HOME environment variable ($HOMEPATH on Win32 systems).
FILES
.ptksh_init
If found in current directory it is read in an evaluated after the mainwindow $mw is created. .ptksh_init can contain any valid perl
code.
~/.ptksh_history
Contains the last 50 lines entered in ptksh session(s).
PITFALLS
It is best not to use "my" in the commands you type into ptksh. For example "my $v" will make $v local just to the command or commands
entered until <Return> is pressed. For a related reason, there are no file-scopy "my" variables in the ptksh code itself (else the user
might trounce on them by accident).
BUGS
Tk::MainLoop function interactively entered or sourced in a init or script file will block ptksh.
SEE ALSO
Tk perldebug
VERSION
VERSION 2.03
AUTHORS
Mike Beller <beller@penvision.com>, Achim Bohnet <ach@mpe.mpg.de>
Copyright (c) 1996 - 1998 Achim Bohnet and Mike Beller. All rights reserved. This program is free software; you can redistribute it and/or
modify it under the same terms as Perl itself.
Tk804.03 2010-05-29 PTKSH(1p)