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

Home » Public Forums » archive » Re: compiling errors in different computers with CW_BGROUP and GET_SCRREEN_SIZE
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
Re: compiling errors in different computers with CW_BGROUP and GET_SCRREEN_SIZE [message #11354] Sat, 21 March 1998 00:00
davidf is currently offline  davidf
Messages: 2866
Registered: September 1996
Senior Member
M. Jesus Ledesma (mledesma@teb.upm.es) writes:

> I am a spanish student, I am developing and aplication for a
> Center in Germany and the last days I've had some strange problems. I
> have my aplication compiling and running here in Spain, but when
> yesterday I sent it to Germany , there it does not compile,
> unbelivebable!. We both have the same development version idl 5.0.2.

You don't say how you are transmitting the file, but I hope
you are not e-mailing it. That almost always introduces
compile problems, usually having to do with the length
of the lines and how the lines are broken by the e-mail
application on either end. Use ftp if at all possible. I
like to zip or otherwise compress files before I ftp them.

Given that the files got there in good shape, I think two
things might be happening. One, it might be that the person
on the other end does NOT have the same files you have,
even if you are using the same version of IDL. For example,
they may have modified their version of CW_BGROUP or they
are using an old one that doesn't accept some of the keywords
you are using, etc.

Use Help, /Source to be sure that you are getting these files
from the same place and that they are, indeed, the same files.

The second thing that may be happening is that tabs in the file
may cause their line to be longer than your line. (You can set the
length of tabs and you can never depend on them. It is best to
use spaces in your code if you are going to be passing it
around to other people.) Depending upon which editor they
are using, these longer lines may be broken in a way that you
didn't expect. Examine the lines of the code to look for bad
line breaks (i.e., lines that don't have line continuation
characters on the ends of them).

These kinds of "file transfer" problems are more common than
you might expect. (Put some files on a web page for other
people to download if you REALLY want to learn about this
in great detail.) It helps a lot if you make a conscious
effort to write SHORT lines of code (about 72 characters
per line, max).

Good luck,

David
-----------------------------------------------------------
David Fanning, Ph.D.
Fanning Software Consulting
E-Mail: davidf@dfanning.com
Phone: 970-221-0438
Coyote's Guide to IDL Programming: http://www.dfanning.com/
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Structure of Structure
Next Topic: Default BUFSIZE

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

Current Time: Fri Oct 10 11:28:55 PDT 2025

Total time taken to generate the page: 0.15522 seconds