FUnit | The testing microframework for PHP | Testing library

I am trying to write a netfilter module. My first attempt.

My Makefile is:

I have #include (no extra spaces) and locate stdio.h shows a few viable options. And yet, when I build, it always says it can't be found. I can include it with a full path #include "/usr/include/stdio.h", but then its own dependencies (features.h) can't be found. I tried specifically sourcing the /usr/include folder which I imagine should already be good to go anyway, but that doesn't help it find it either. So... what the heck? I'm also building with sudo privileges. I can't fathom a good reason for it to not be found.

output from make V=1 VERBOSE=1

I have a code where I have to do a great deal of file I/O and as such would like a pretty efficient way of dealing with the following problem. For the sake of convenience, my code always write to restart files only the real part, coded as follows:

I want to not display an icon for the mobile menu. But I'm not sure how to select this class. It's inside a menu.

I have been trying to writing a program to implement polynomials on arbitrary field, a mathematical structure. I chose Haskell as the programming language, and I used the GADTs language extension. However, I don’t understand why GHCi can’t deduce the constraints of a.

The context:

I am trying to write a function that extracts a specified line from a given file. My function to do so takes two arguments:

1. fUnit: this is the numerical identifier of the given file.
2. fLine: this is the line number that I'd like to extract. If the value of this input is -1, then the function will return the last line of the file (in my work, this is the functionality I need the most).

I have wrapped this function inside a module (routines.f95), as shown:

I know the title is a bit confusing. Let me clarify my problem with a little background:

My program behaves strangely when I compile it with -O1 flag vs -O0 flag in terms of execution time. I know -O1 flag does many optimizations such as fauto-inc-dec -fbranch-count-reg -fcombine-stack-adjustments (More than 40 according to the man page). To figure out which optimization(s) cause this behavior, I plan to remove flags one at a time then compile and test to see if something changes.

Before doing this experiment, I want to make sure that the program compiled with -O1 and the program compiled with -O0 plus all flags which -O1 enables (Lets call -O0+) behave similarly. Actually, I expect both method should produce the same binary file since the same optimization flags are enabled.

Compilation with O1

I created my own progressbar (TProgressBalken) consisting of a TRectangle, within that there's another TRectangle (a) with a different color, its width varies with the progress value (0..100). Finally a Tlabel sits on top of it displaying the current value as text. All works fine when creating this component at runtime.

When dropping this on a new multidevice form (IDE set to 32-bit windows) it also works fine. But when switching IDE to Android, TRectangle(a) and Label are duplicated in the fmx file, I see now the label painted twice. And Delphi complains of duplicated items.

Originally I assigned no name to TRectangle(a) and Label, but Delphi complained, so I assigned names during creation, but the actual problem remains.

Any idea what is missing?

This is my component:

MSDN's truetype font article (https://docs.microsoft.com/en-us/typography/opentype/otspec160/ttch01) gives the following for converting FUnits to pixels:

Values in the em square are converted to values in the pixel coordinate system by multiplying them by a scale. This scale is:

pointSize * resolution / ( 72 points per inch * units_per_em )

where pointSize is the size at which the glyph is to be displayed, and resolution is the resolution of the output device. The 72 in the denominator reflects the number of points per inch.

For example, assume that a glyph feature is 550 FUnits in length on a 72 dpi screen at 18 point. There are 2048 units per em. The following calculation reveals that the feature is 4.83 pixels long.

550 * 18 * 72 / ( 72 * 2048 ) = 4.83

Questions:

1. It says "pointSize is the size at which the glyph is to be displayed." How does one compute this, and what units is it in?
2. It says "resolution is the resolution of the output device". Is this in DPI? Where would I get this information?
3. It says "72 in the denominator reflects the number of points per inch." Is this related to DPI or no?
4. In the example, it says '18 point'. Is this 18 used in computing the resolution or the pointSize?

Unfortunately, Apple's documentation is more or less the same, and other than that there are barely any resources other than just reading the source code of stb_truetype.