comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Giant arrays!
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Giant arrays! [message #9420] Fri, 27 June 1997 00:00 Go to next message
Ben Krasnow is currently offline  Ben Krasnow
Messages: 1
Registered: June 1997
Junior Member
Hi all! I am new to PV-WAVE, and I have a 'can it do this' question:
I made a simple program that loads a three dimensional(256x256x30
images) image array, selects one image, and then uses assoc to 'copy'
one of the images to a two dimensional array. Next I want to transfer
that into a one-dimensional array so I can use sort on it. the problem
is the one-dimensional array has to be 65536 elements, to hold the
single 256x256 image's data. PV-WAVE bombs, and says something to the
tune of 'too many elements'. Is there another way to do this, without
breaking the array up(I have to use sort on it)? Thanks
Re: Giant arrays! [message #9502 is a reply to message #9420] Fri, 11 July 1997 00:00 Go to previous message
David Ritscher is currently offline  David Ritscher
Messages: 30
Registered: August 1995
Member
Mary Jo Brodzik writes:
>> P.S. Anybody else want to join in a campaign for a system variable that
>> switches the default literal integer to long rather than short? I've
>> been bit too many times...

> Yes, now that would be useful, I've been bitten a number of times,
> myself. And although I try to warn new IDL users, this problem
> continues to bite them, too!

Do you mean that
i = 2
should produce a something other than a 2-byte integer?
I think we should discuss this problem after the year 2000 :-)

IDL 5.0 has finally fixed the 'enhanced feature' of not being able to
differentiate between an array a(3) and a function call
my_function(3). I think it is time for a language reform, where a
system variable tells the interpreter when to interpret code as
vintage code, so, for example,
!LANGUAGE_LEVEL = 1
at the beginning of a routine (i.e., one I wrote years ago) would tell
the interpreter to default to 2-byte integers, arrays with parenthesis
for delimiters, etc. With such a mechanism in place, then RSI and VNI
would be free to update the basic language structure while leaving our
old code in a functional state.

What would other good additions entail? A syntax that follows C++
more closely would be a good start (concerning use of '(', '[", '{',
etc.) Other suggestions??

Tschuess,

David Ritscher


--
David Ritscher
Zentralinstitut fuer Biomedizinische Technik Tel: ++49 (731) 502 5313
Albert-Einstein-Allee 47 Fax: ++49 (731) 502 5315
Universitaet Ulm Internet:
D-89069 ULM
david.ritscher@zibmt.uni-ulm.de
Germany
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: How to use "defroi.pro" in widget applications
Next Topic: 2 cent tip: Faster way to plot millions of points

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 13:45:36 PDT 2025

Total time taken to generate the page: 0.00591 seconds