Click here to Skip to main content
12,633,764 members (29,305 online)
Click here to Skip to main content
Add your own
alternative version


23 bookmarked

Lint: Large Integer Object Library

, 15 Dec 2005
Rate this:
Please Sign up or sign in to vote.
Lint is a signed large integer data type class library.


Lint is a signed large integer data type class library that supports all mathematical operators available to other intrinsic integer data types. The precision is not arbitrary as in other available libraries. Rather, the number of bits that make up a lint variable is dependent on the value of a #define directive declared in the header file.


So why yet another large integer library? Several reasons, among which:

  • I wanted a class that supported all possible overloaded operators so that I could use a lint just exactly like I might use an intrinsic data type such as an int or long. None of the free implementations I could find seemed to support all over-loadable operators.
  • I wanted a class that was specifically created with Visual C++ and IA-32 based PC architecture in mind. I didn't want a library that sacrificed execution speed for the sake of cross-compiler and cross-platform compatibility. I wanted a library that I could optimize with in-line assembly code.
  • I wanted a class whose methods were as fast and efficient as possible. Arbitrary-precision logic and floating point logic bring with them a performance hit. This library is efficient because precision is not arbitrary and all operations are strictly integer based. In this way, I could write highly optimized assembly routines given a known data type and size.

Using the code

Once you include the header file in your source, using a lint is similar to using any other numeric data type in C++. The few notable exceptions are in declaration, assignment, and output.

#include <span class="code-string">"lint.h"</span>

Points of Interest

Implementing the conditional testing was a real bugger. My implementation works, but I think there must be a better way to do it. There are additional things I'd like to do to the library as well.

  • Possibly implement faster multiplication and division algorithms using FFT, Barrett, or whatever.
  • Add capability to assign a value using a string in any radix from 2 to 36, not just base 10.
  • Make use of MMX and XMM registers for even faster inline assembly.


Initial releaseDecember 4, 2005by Jeremy A. Wilson 
UpdateDecember 6, 2005by Jeremy A. WilsonDiscovered my comparison operators were using the wrong assembly instruction which failed to report correctly if the MSB was set in one DWORD and not the other.
UpdateDecember 9, 2005by Jeremy A. WilsonAfter further review of my December 6th fix, I realized I still hadn't fixed it right. Now I have. I also ran a complete set of comparisons.


This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here


About the Author

Jeremy A. Wilson
Software Developer
United States United States
I've worked in the industry since 1992. After the dot com crash of 2001, I went back to school and graduated from the University of North Texas in 2005. I now live in the Dallas area with my wife and two children, and work as a senior software engineer for a local company.

I first learned to program on a Commodore 64 when I was 12 years old. The rest is history...

You may also be interested in...


Comments and Discussions

QuestionRe: Unfortunately does not seem to work under MSVC Pin
Zsuzsi22-May-06 5:25
memberZsuzsi22-May-06 5:25 
GeneralConst correctness Pin
HobbitCoder17-Dec-05 10:37
memberHobbitCoder17-Dec-05 10:37 
GeneralRe: Const correctness Pin
Jeremy A. Wilson23-Dec-05 10:57
memberJeremy A. Wilson23-Dec-05 10:57 
JokeBUG Pin
kevincpp15-Dec-05 23:02
memberkevincpp15-Dec-05 23:02 
have found the bug:

for VC compiler, at start of a function, will fill the stack with 0xcccccccc, using "rep stos". and many rep stos in your coding. when you insert std, rep stosd..., you must restore direction flag using cld. in order to avoid error, you'd better insert pushfd at begin, and popfd at end in _asm{}.

again: can you finish the hex string? "abcdef0123456789"...?

for example:
void lint::copy_from(lint& rvalue) {
// here, the compile will insert code like rep stos...
long *first_addr = &data[0];
long *addr_s = &[0];

_asm {
pushfd; // push the flag
mov esi, addr_s;
mov edi, first_addr;
mov ecx, LINT_LENGTH;
rep movsd;
popfd;// pop the flag

GeneralRe: BUG Pin
Jeremy A. Wilson16-Dec-05 22:37
memberJeremy A. Wilson16-Dec-05 22:37 
GeneralRe: BUG Pin
Toby Opferman20-Jan-06 8:20
memberToby Opferman20-Jan-06 8:20 
GeneralRe: BUG Pin
MadFalcon7-Jul-06 13:12
memberMadFalcon7-Jul-06 13:12 
QuestionRe: BUG Pin
Mohammed Hossny23-Aug-06 18:06
memberMohammed Hossny23-Aug-06 18:06 
GeneralNice Work! Pin
yafan15-Dec-05 11:51
memberyafan15-Dec-05 11:51 
Generala few comments Pin
Warren D Stevens15-Dec-05 9:49
memberWarren D Stevens15-Dec-05 9:49 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web02 | 2.8.161208.2 | Last Updated 15 Dec 2005
Article Copyright 2005 by Jeremy A. Wilson
Everything else Copyright © CodeProject, 1999-2016
Layout: fixed | fluid