|
|
Sponsored Content
Top Forums
Programming
help with data type sizes
Post 302488288 by Corona688 on Sunday 16th of January 2011 01:53:17 PM
|
|
10 More Discussions You Might Find Interesting
1. Programming
Hi all,
Can anyone tell me a little about the datatype FILE, which represents stream. What does its structure look like, and in which header file is it defined and so on...
Ex :
FILE *fp ;
fp = fopen("filename", "w") ; (6 Replies)
Discussion started by: milhan
6 Replies
2. Programming
Hi,
I am trying to understand an very old C program.
....
time_t start, end;
ptr = localtime(&start);
...
fprintf(out, "%-35s 01 %5s %2s %10d 1 5 /tty/M%d/%02d %24s", buffer3, job, ver, start, mach_num,atoi(buffer), asctime(ptr));
fprintf(out, "%-35s 03 %5s %2s %10d 1 5... (9 Replies)
Discussion started by: whatisthis
9 Replies
3. Programming
I am writing some code to do analysis on the file system (HP-UX 11.11).
I am using stat(..) to get file information. My problem is that the file-size may exceed the data types defined in 'sys/stat.h' & 'sys/types.h' respectively.
Thus file-sizes in the Giga-byte range are not read correctly.... (2 Replies)
Discussion started by: ALTRUNVRSOFLN
2 Replies
4. AIX
Hello,
I get this message : "Value too large to be stored in data type" when I try to open a 3Gb file.
Can someone helps me to resolve the problem.
Thank you very much (5 Replies)
Discussion started by: limame
5 Replies
5. UNIX for Dummies Questions & Answers
I have seen it done at my job before, there is a command that will make a notepad and show the directorie path, subfolders, and size of the subfolders? But i dont want it to go lower than 2 levels for example:
folder_01 10 GB
subfolder_02 10 GB
subfolder_03 10 GB... (4 Replies)
Discussion started by: JUSSAN007
4 Replies
6. Shell Programming and Scripting
I am using perl 5.8.0.
I need to check some values to see it they are floats. Our system does not have Data::Types so I can't use is_float. Is there something else that I can use? The only thing in Data is Dump.pm. I am not allowed to download anything to our system so I have to use what I have.... (3 Replies)
Discussion started by: ajgwin
3 Replies
7. UNIX for Advanced & Expert Users
Dear All,
How internally memory allocated when we declare the float data type.
how many bytes allocated for decimal and how many bytes for fraction.
kindly help me in this regards. (2 Replies)
Discussion started by: rajamohan
2 Replies
8. Shell Programming and Scripting
I'm not a unix guy so excuses my ignorance... I'm the database ETL guy.
I'm trying to be proactive and devise a plan B for a ETL process where I expect a file 10X larger than what I process daily for a recast job. The ETL may handle it but I just don't know.
This file may need to be split... (3 Replies)
Discussion started by: john091
3 Replies
9. Web Development
Hi everybody,
I`m very new with PHP and Databases and I having the follow issue with prices data..
The original information is in CSV files.
The prices have formatted with commas and dots as follow:
12,300.99 -->(thousands separated by commas)
3,500.25 -->(thousands separated... (10 Replies)
Discussion started by: cgkmal
10 Replies
10. Programming
This is from a program I wrote over in 1998 that I am trying to compile on a linux machine:
void write_line (FILE *fp, int rec_no, line_rec *arec)
{
fpos_t woffset;
woffset = (rec_no - 1) * sizeof(line_rec);
fsetpos(fp,&woffset);
fwrite(arec,sizeof(line_rec),1,fp);
}On the line... (2 Replies)
Discussion started by: wbport
2 Replies
LEARN ABOUT HPUX
stdint
stdint(5) File Formats Manual stdint(5) NAME
stdint - integer types SYNOPSIS
DESCRIPTION
This header file defines sets of integer types having specified widths and corresponding sets of macros. It also defines macros that spec- ify limits of integer types corresponding to types defined in other standard headers. Since not all implementations are required to support all of the integer sizes defined in this manual page, the proper way to see if a par- ticular size of an integer is supported on the current implementation is to test the symbol that defines its maximum value. For example, if tests false, then that implementation does not support 64-bit unsigned signed integers. This header file defines the following integer data types for 8, 16, 32, and 64 bits. largest signed integer data type supported by implementation 8-bit signed integer 16-bit signed integer 32-bit signed integer 64-bit signed integer largest unsigned integer data type supported by implementation 8-bit unsigned integer 16-bit unsigned integer 32-bit unsigned integer 64-bit unsigned integer The following two data types are signed and unsigned integer data types that are large enough to hold a pointer. A pointer can be moved to or from these data types without corruption. signed integer type that is large enough to hold a pointer unsigned integer type that is large enough to hold a pointer This header file defines the following integer data types for determining the most efficient data types to use for integer values on a par- ticular implementation. most efficient signed integer data type supported by implementation most efficient signed integer of at least 8 bits most efficient signed integer of at least 16 bits most efficient signed integer of at least 32 bits most efficient signed integer of at least 64 bits most efficient unsigned integer data type supported by implementation most efficient unsigned integer of at least 8 bits most efficient unsigned integer of at least 16 bits most efficient unsigned integer of at least 32 bits most efficient unsigned integer of at least 64 bits This header file defines the following integer data types for compatibility with systems that do not fit the 16-bit or 32-bit word size model. These data types define the signed and unsigned integers of at least 8, 16, 32, and 64 bits. smallest signed integer of at least 8 bits smallest signed integer of at least 16 bits smallest signed integer of at least 32 bits smallest signed integer of at least 64 bits smallest unsigned integer of at least 8 bits smallest unsigned integer of at least 16 bits smallest unsigned integer of at least 32 bits smallest unsigned integer of at least 64 bits The following macros define the minimum and maximum values that can be stored in the above data types. minimum value that can be stored in the largest integer data type maximum value that can be stored in the largest signed integer data type maximum value that can be stored in the largest unsigned integer data type minimum value that can be stored in the most efficient integer data type maximum value that can be stored in the most efficient signed integer data type maximum value that can be stored in the most efficient unsigned integer data type minimum value that can be stored in an data type minimum value that can be stored in an data type minimum value that can be stored in an data type minimum value that can be stored in an data type maximum value that can be stored in an data type maximum value that can be stored in an data type maximum value that can be stored in an data type maximum value that can be stored in an data type maximum value that can be stored in an data type maximum value that can be stored in an data type maximum value that can be stored in an data type maximum value that can be stored in an data type" minimum value that can be stored in an data type minimum value that can be stored in an data type" minimum value that can be stored in an data type minimum value that can be stored in an data type maximum value that can be stored in an data type maximum value that can be stored in an data type maximum value that can be stored in an data type maximum value that can be stored in an data type minimum value that can be stored in an data type minimum value that can be stored in an data type minimum value that can be stored in an data type minimum value that can be stored in an data type maximum value that can be stored in an data type maximum value that can be stored in an data type maximum value that can be stored in an data type maximum value that can be stored in an data type The following macros specify the maximum and minimum limits of integer types corresponding to types defined in other standard headers. All these values are implementation defined. minimum value that can be stored in data type maximum value that can be stored in data type minimum value that can be stored in data type maximum value that can be stored in data type maximum value that can be stored in data type minimum value that can be stored in data type maximum value that can be stored in data type minimum value that can be stored in data type maximum value that can be stored in data type The following macros expand to integer constant expressions suitable for initializing objects that have integer types corresponding to types defined in header. Macros For Minimum-Width Integer Constant Expressions The macro expands to an integer constant expression corresponding to the type The macro expands to an integer constant expression corresponding to the type For example, if is a name for the type then might expand to the integer constant Macros For Greatest-Width Integer Constant Expressions The following macro expands to an integer constant expression having the value specified by its argument and the type The following macro expands to an integer constant expression having the value specified by its argument and the type FILES
SEE ALSO
inttypes(5), standards(5), <stddef.h>, <wchar.h>, <signal.h>. stdint(5)