Wol
In BASIC, *EVERYTHING* is a string (apart from file variables).
Therefore any comparison should be valid.
To be more precise, no.
UniVerse Basic is a run-time typed language (like PHP) not a string
language. So it gets the performance and storage benefits of real types, and
coerces between
If your file is opened, then comparing it to an empty string is what will
cause an invalid data type error.
WHY!!!
If the datatypes don't match, then the result of the comparison is
FALSE, not INVALID.
It is logically correct to do such a comparison. The result I am looking
for is the
In message 321088.49154...@web36901.mail.mud.yahoo.com, Jacques G.
jacque...@yahoo.com writes
If your file is opened, then comparing it to an empty string is what
will cause an invalid data type error.
WHY!!!
If the datatypes don't match, then the result of the comparison is
FALSE, not
AM
To: U2 Users List
Subject: Re: [U2] OPENSEQ and Abnormal termination of UV
Yes, I see your point. I wonder if the integer gets treated like a
string in the first instance. I wonder what the result with FILEVARS1
would be.
-John
-Original Message-
From: u2-users-boun
...That's what I absolutely HATE about artificial stupidity. It
thinks it knows better than me, and gives me what it thinks I should
have, not what I asked for.
Then again, I can't imagine it thinks it should CRASH! :-o
Bill
Oh - that reminds me of something else I'd call a bug. It might well have been
fixed by now (I met it in 9.6) but you couldn't safely use a file variable in
an IF statement. Can't remember the details, but it was something like
FVAR =
some conditional code
OPEN FILE TO FVAR
more code
IF FVAR
, ARGV_IN, ARGV_OUT)
This means each program calling MYSUB has to be modified.
- Original Message
From: John Hester jhes...@momtex.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Tue, May 18, 2010 3:31:25 PM
Subject: Re: [U2] OPENSEQ and Abnormal termination of UV
Reading my
In message 536051.22442...@web36905.mail.mud.yahoo.com, Jacques G.
jacque...@yahoo.com writes
Oh - that reminds me of something else I'd call a bug. It might well have been
fixed by now (I met it in 9.6) but you couldn't safely use a file variable
in an IF statement. Can't remember the details,
Anthony W. Youngman pi...@thewolery.demon.co.uk
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site
.
Youngman
Sent: Tuesday, May 18, 2010 7:45 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] OPENSEQ and Abnormal termination of UV
In message
e6179e13392ec14aabcd5272c3aedd61124ec...@exchangesvr.momtex.com, John
Hester jhes...@momtex.com writes
I think it's something along those lines, but I
To: U2 Users List
Subject: Re: [U2] OPENSEQ and Abnormal termination of UV
Yes, I see your point. I wonder if the integer gets treated like a
string in the first instance. I wonder what the result with FILEVARS1
would be.
-John
-Original Message-
From: u2-users-boun
!! ??
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of John Hester
Sent: 18 May 2010 20:31
To: U2 Users List
Subject: Re: [U2] OPENSEQ and Abnormal termination of UV
Reading my own response just made me realize what's going on. I
as a pointer !! ??
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of John Hester
Sent: 18 May 2010 20:31
To: U2 Users List
Subject: Re: [U2] OPENSEQ and Abnormal termination of UV
Reading my own response just made me realize
Looks like putting a sequential file in a dimensioned array makes
it go out and reserve a block of memory the size of the entire file.
Doubtful..
I'm guessing under the hood the array will resolve to a series of pointers
somewhere down the track, but those pointers will need to be cast to
-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Anthony W.
Youngman
Sent: Tuesday, May 18, 2010 7:45 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] OPENSEQ and Abnormal termination of UV
In message
e6179e13392ec14aabcd5272c3aedd61124ec
Does anyone knows what is happening here:
I am trying to open a text file (over 4Gb) using OPENSEQ and storing the file
variable into a array as follows:
COMMON /MYPROG/ FILEVARS(10)
OPENSEQ /tmp/file.txt to FILEVARS(1) ELSE ...
This operation results abnormal termination with fault type error
To: u2-users@listserver.u2ug.org
Subject: [U2] OPENSEQ and Abnormal termination of UV
Does anyone knows what is happening here:
I am trying to open a text file (over 4Gb) using OPENSEQ and storing the
file variable into a array as follows:
COMMON /MYPROG/ FILEVARS(10)
OPENSEQ /tmp/file.txt to FILEVARS(1
Sent: Mon May 17 14:55:30 2010
Subject: [U2] OPENSEQ and Abnormal termination of UV
Does anyone knows what is happening here:
I am trying to open a text file (over 4Gb) using OPENSEQ and storing the file
variable into a array as follows:
COMMON /MYPROG/ FILEVARS(10)
OPENSEQ /tmp/file.txt
List
Subject: Re: [U2] OPENSEQ and Abnormal termination of UV
Just for giggles... what happens if you...
OPENSEQ '/tmp/file.txt' TO FV.TEMP ELSE ...
FILEVARS(1) = FV.TEMP
??
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org
-boun...@listserver.u2ug.org] On Behalf Of Dan Goble
Sent: Monday, May 17, 2010 12:00 PM
To: 'u2-users@listserver.u2ug.org'
Subject: Re: [U2] OPENSEQ and Abnormal termination of UV
You may want to check with your Systems Administrator to be sure your file
system is setup to support files larger
Sent: Monday, May 17, 2010 2:09 PM
To: U2 Users List
Subject: Re: [U2] OPENSEQ and Abnormal termination of UV
I already tried that. Same Error and the fault occurring at FILEVAR(1) =
FV.TEMP line.
Thanks,
Rajesh
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2
...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Rajesh Menon
Sent: Monday, May 17, 2010 1:56 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] OPENSEQ and Abnormal termination of UV
Does anyone knows what is happening here:
I am trying to open a text file (over 4Gb) using OPENSEQ
de mayo de 2010 16:12
Para: U2 Users List
Asunto: Re: [U2] OPENSEQ and Abnormal termination of UV
Yes file system is setup to support +2Gb files. As I mentioned I can open
the file using a scalar file variable. Problem happening only with the
combination of +2Gb and using array variable.
Thanks
program PTEST at address 5a.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Marc A
Hilbert
Sent: Monday, May 17, 2010 3:41 PM
To: 'U2 Users List'
Subject: Re: [U2] OPENSEQ and Abnormal termination of UV
What
Users List'
Subject: Re: [U2] OPENSEQ and Abnormal termination of UV
Let me see, can it be because you are trying to cram over 4 GB of data
into
a single cell. Unlike the OPEN statement that just puts the file
variable
into a variable, the OPENSEQ opens the whole file to the variable.
Jerry Banker
A
Hilbert
Sent: Monday, May 17, 2010 3:41 PM
To: 'U2 Users List'
Subject: Re: [U2] OPENSEQ and Abnormal termination of UV
What happens wif you open to regular variable then pass it over to the
array:
OPENSEQ TO FVAR
FILEVARS(1) = FVAR
?
Regards,
Marc
-Mensaje original-
De: u2-users
26 matches
Mail list logo
