public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Fleur Kelpin <fleur@bio.vu.nl>
To: Abraham David Smith <abrahamsmith@students.wisc.edu>
Cc: <gsl-discuss@sources.redhat.com>
Subject: Re: gsl_complex_rect undefined?
Date: Tue, 18 Dec 2001 09:37:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0112181833270.20798-100000@monodon> (raw)
Message-ID: <20011218093700.cOGq94Txit1wTghxJmEyl_vyIQbD1XtiDbM60TkJje8@z> (raw)
In-Reply-To: <20011218113006.A22589@euclid.dsl.wisc.edu>

Hi,

You need the include file gsl_complex_math.h
In case of similar trouble, grep the include files:
(in the /usr/local/include or similar:)
>cd gsl/complex
>grep gsl_complex_rect *.h
gsl_complex_math.h:gsl_complex gsl_complex_rect (double x, double y);  /*
r= real+i*imag */
gsl_complex_math.h:gsl_complex_rect (double x, double y)
gsl_complex_math.h:#define GSL_COMPLEX_ONE (gsl_complex_rect(1.0,0.0))
gsl_complex_math.h:#define GSL_COMPLEX_ZERO (gsl_complex_rect(0.0,0.0))
gsl_complex_math.h:#define GSL_COMPLEX_NEGONE (gsl_complex_rect(-1.0,0.0))

Greetings,
Fleur Kelpin

On Tue, 18 Dec 2001, Abraham David Smith wrote:

>
> I am trying to use GSL 1.0 on an ix86 running an essentially normal RedHat
> Linux 7.1 installation (with all of RedHat's published patches applied
> to gcc, etc).
>
> Consider the following code snippet:
>
> #include <iostream.h>
> #include <gsl/gsl_complex.h>
> void main()
>   {
>   gsl_complex a = gsl_complex_rect(1.0,2.0);
>   cout << GSL_REAL(a) << ", " << GSL_IMAG(a) << endl;
>   GSL_SET_COMPLEX (&a, 3.0, 4.0);
>   cout << GSL_REAL(a) << ", " << GSL_IMAG(a) << endl;
>   }
>
> Compiling this with g++ gives:
>
> testcomplex.cpp: In function `int main (...)':
> testcomplex.cpp:9: `gsl_complex_rect' undeclared (first use this
> function)
> testcomplex.cpp:9: (Each undeclared identifier is reported only once
> for each function it appears in.)
>
>
> now consider the snippet:
>
> #include <iostream.h>
> #include <gsl/gsl_complex.h>
> void main()
>   {
>   gsl_complex a;
>   cout << GSL_REAL(a) << ", " << GSL_IMAG(a) << endl;
>   GSL_SET_COMPLEX (&a, 3.0, 4.0);
>   cout << GSL_REAL(a) << ", " << GSL_IMAG(a) << endl;
>   }
>
>
> this compiles and gives:
> 2.10391, 7.02217
> 3, 4
>
>
>
> According to page 18 of the GSL manual
> [ http://sources.redhat.com/gsl/ref/gsl-ref_5.html#SEC34 ], the function
> gsl_complex_rect should be defined.  What's up here?
>
>
> --
> # Abraham David Smith       UW--Madison Mathematics/Physics Undergraduate [*] #
> # <abrahamsmith@students.wisc.edu>  Y!:abrahamdavidsmith  AOL-IM:abrahamsmith #
> # http://euclid.dsl.wisc.edu/~abe     Molon Labe!       Defend your rights!   #
> # [*]: The views I express are not necessarily those of the UW--Madison, etc. #
>

  parent reply	other threads:[~2001-12-18  9:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 13:20 Abraham David Smith
2001-12-10  6:38 ` Abraham David Smith
2001-12-18  9:30 ` Abraham David Smith
2001-12-19 13:20 ` Abraham David Smith
2001-12-19 13:20 ` Tisserand Patrice
2001-12-10 13:11   ` Tisserand Patrice
2001-12-18  9:39   ` Tisserand Patrice
2001-12-19 13:20 ` Fleur Kelpin [this message]
2001-12-10 12:37   ` Fleur Kelpin
2001-12-18  9:37   ` Fleur Kelpin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.GSO.4.33.0112181833270.20798-100000@monodon \
    --to=fleur@bio.vu.nl \
    --cc=abrahamsmith@students.wisc.edu \
    --cc=gsl-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).