From: Jan Stary <hans@stare.cz>
To: sox-devel@lists.sourceforge.net
Subject: Re: using lpc
Date: Sun, 9 Jun 2024 22:22:44 +0200 [thread overview]
Message-ID: <ZmYPFAAN3J6_Nnef@www.stare.cz> (raw)
In-Reply-To: <ZmWfOj-fY--QOuJk@www.stare.cz>
On Jun 09 14:25:30, hans@stare.cz wrote:
> #if defined(INT_MAX) && defined(INT_MIN) && INT_MAX==2147483647 && INT_MIN==(-2147483647-1)
> typedef int INT32;
> #elif defined(LONG_MAX) && defined(LONG_MIN) && LONG_MAX==2147483647 && LONG_MIN==(-2147483647-1)
> typedef long INT32;
> #else
> #error Unable to determine an appropriate definition for INT32.
> #endif
Wow. This has been _introduced_ in 2011, REPLACING
typedef int16_t INT16;
typedef int32_t INT32;
in commit 88eec9c75d0a23c6c4d5d61af76c6ebd56b82b51
along with other "Portability fixes for sox.h".
So no, this is not the original LPC code.
Luckily, Andy Fingerhut just published this:
https://github.com/jafingerhut/lpc10
Jan
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
prev parent reply other threads:[~2024-06-09 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 7:43 using lpc Jan Stary
2024-06-09 12:25 ` Jan Stary
2024-06-09 12:27 ` Jan Stary
2024-06-09 20:22 ` Jan Stary [this message]
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZmYPFAAN3J6_Nnef@www.stare.cz \
--to=sox-devel@lists.sourceforge.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
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).