>From: Alex Rhomberg <[EMAIL PROTECTED]>
You could try test -eq, it returns an error if non-integer parameters are
used:
#!/bin/sh
test $1 -eq $1 2>/dev/null
if test $? -eq 2; then
echo non integer
else
echo integer
fi
- Alex
pn] Thanks, that's elegant when I need to work o
On Tue, 8 Jul 2003, Jose Luis Abuelo Sebio wrote:
[...]
> I have readed the Bering Devlopment Guide, but
> things are not pretty clear for me, so maybe any of
> you could have the time to explain me, carefully, how
> for instance, the package atmtools.lrp was created and
> compilated.
Read ht
Hi Charles,
On Tue, 2003-07-08 at 13:32, Charles Steinkuehler wrote:
> Peter Nosko wrote:
> > pn] Forgive me; I can't Google this for some reason.
> >
> > pn] Is there an elegant way to test a positional parameter for being numeric (so
> > that I don't
> > assign a string to a numeric variable)?
Hi everyone,
My name is Luis and I am studying C.S. at my
University in Spain. I am getting interest for this
proyect, but sometimes I feel that I don´t know enough
to understand the process of some projects you talk
here about.
I did a job about Vlan using LEAF Bering rc 4 and it
was prett
Peter Nosko wrote:
-Original Message-
From: Charles Steinkuehler
To get around this problem (if necessary), you'll either need to
recursively parse each digit of the parameter to see if it's a number
(ugly, but relies only on built-in shell commands)...something like:
pn] Somehow I knew
