From: Brian Gough <bjg@network-theory.co.uk>
To: gsl-discuss@sources.redhat.com
Subject: forwarded message from Brian Gough
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <15297.23867.609198.188602@debian> (raw)
To : Rodney Sparapani <rsparapa at mcw dot edu>
Subject : Re: Missing header in GSL 0.9.3
From : Brian Gough <bjg at network-theory dot co dot uk>
Date : Mon, 8 Oct 2001 09:00:17 +0100 (BST)
References : < 15295.17919.433703.424674@debian ><9B6D336E-BB84-11D5-B173-003065D59DC8@mcw.edu>
Rodney Sparapani writes:
> I've got this header file in vector:
> -rw-r--r-- 1 rodney staff 8554 Sep 14 18:16
> gsl_vector_complex_long_double.
> Why it doesn't have a .h extension? Perhaps, there is a logical limit
> to the length of a filename. I know there is a GNU e-lisp coding
> standard that requires files not to exceed 10.3. Maybe this is why.
Apparently filenames are limited to 31 characters. Not sure what you
can do about that.
next reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 Brian Gough [this message]
2002-08-11 15:37 Brian Gough
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=15297.23867.609198.188602@debian \
--to=bjg@network-theory.co.uk \
--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).