09-17-2018
This problem was fixed by removing all <table> elements in the code for posts and replacing them with <div> elements.
That's the problem with running code which is 10 years old.
4 More Discussions You Might Find Interesting
1. Hardware
I have read a document which tells me the following 4 things are done by the RAM embedded on disk driver controller. But I don't know what's difference between buffer and cache. Thanks!
RAM on disk drive controllers
1 firmware
2 speed matching buffer
3 prefetching buffer
4 cache (1 Reply)
Discussion started by: 915086731
1 Replies
2. What is on Your Mind?
Making some progress using CSS from Bootstrap; changing table classes to the Bootstrap "table" class and wrapping those tables in a div with a scroll bar.
So, the good news is that now each post with large blocks of code that exceeds the width of the screen will have a scrollbar; but the bad... (0 Replies)
Discussion started by: Neo
0 Replies
3. What is on Your Mind?
Hey,
Success!
I have converted the posts (each of the main posts) from table tags to div tags and the problem with the scroll bar and code tags is fixed, as I predicted (Yay!).
Now I'm testing this (only I see the new results because the new code is restricted to my userid) but I would... (27 Replies)
Discussion started by: Neo
27 Replies
4. What is on Your Mind?
By special request, and long overdue, I have updated our "code tags" video and so now we have:
How to Use Code Tags and Format Posts @UNIX.com in 4K
https://youtu.be/4BuPvWJV__k (3 Replies)
Discussion started by: Neo
3 Replies
fixadd(3alleg4) Allegro manual fixadd(3alleg4)
NAME
fixadd - Safe function to add fixed point numbers clamping overflow. Allegro game programming library.
SYNOPSIS
#include <allegro.h>
fixed fixadd(fixed x, fixed y);
DESCRIPTION
Although fixed point numbers can be added with the normal '+' integer operator, that doesn't provide any protection against overflow. If
overflow is a problem, you should use this function instead. It is slower than using integer operators, but if an overflow occurs it will
set `errno' and clamp the result, rather than just letting it wrap. Example:
fixed result;
/* This will put 5035 into `result'. */
result = fixadd(itofix(5000), itofix(35));
/* Sets `errno' and puts -32768 into `result'. */
result = fixadd(itofix(-31000), itofix(-3000));
ASSERT(!errno); /* This will fail. */
RETURN VALUE
Returns the clamped result of adding `x' to `y', setting `errno' to ERANGE if there was an overflow.
SEE ALSO
fixsub(3alleg4), fixmul(3alleg4), fixdiv(3alleg4)
Allegro version 4.4.2 fixadd(3alleg4)