From Newsgroup: comp.lang.c

i was talking on that recently but now i making some cleaning in my
green fire library i watch on things after rethinking that concept
and yet more see an urging need of this pinpoints in c

without it is really a mess

two examples

1) i got a code that measures usage of ram of my app (as i like to see
it on screen) and of course i got a function for it in my windows_ut
file.. (which is ok) i draw it in my diagnostic_hud file (also ok)
but i also need a point where i call it (to change how often i call it
(i dont acll it every frame but once some n frames) - and this is NOT
okay


its not okay as i must damn find it thats forst second is i need to
pin many things in this window_setup file but they are not exactly a
part of that file becouse they are only pinned here - need a point to
pin and thet mess of pinned clien is a mes that dont belong to
windows_setup file

it needs to be emphasised and it is more and more clear..

c needs a pin points

whet more pin points are importat to be reckognized in programmer
consciousnes becouse in present state of things it is what makes
or may make some trouble

2) if yu work with ai ai give pices of code but te trouble is often
related to lack of pinpoints becouse you would take the pice and
put it in where you need to put it if you would have pin points defined
you could just replace old separate block and pinpoints would hold












--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

fir pisze:

i was talking on that recently but now i making some cleaning in my
green fire library i watch on things after rethinking that concept
and yet more see an urging need of this pinpoints in c

without it is really a mess

two examples

1) i got a code that measures usage of ram of my app (as i like to see
it on screen)-a-a and of course i got a function for it in my windows_ut file.. (which is ok) i draw it in my diagnostic_hud file (also ok)
but i also need a point where i call it (to change how often i call it
(i dont acll it every frame but once some n frames) - and this is NOT
okay

its not okay as i must damn find it thats forst second is i need to
pin many things in this window_setup file but they are not exactly a
part of that file becouse they are only pinned here - need a point to
pin and thet mess of pinned clien is a mes that dont belong to
windows_setup file

it needs to be emphasised and it is more and more clear..

c needs a pin points

whet more pin points are importat to be reckognized in programmer consciousnes becouse in present state of things it is what makes
or may make some trouble

2) if yu work with ai ai give pices of code but te trouble is often
related to lack of pinpoints becouse you would take the pice and
put it in where you need to put it if you would have pin points defined
you could just replace old separate block and pinpoints would hold

how the syntax tu use i think c labels could be used like


some()
{
pre_blit:
blit();
post_blit:

}

foo() @ pre_blit
{
printf("assas");
}

maybe other sign that @ but something like that


some could say that ponpint could be function
like pre_blit()
and you could call it with calback to call
pre_blit(my_code);
but big problem is that these function need
to be put somewhere on the other side (not here)
and that spoils the thing


nte for example in my winapi library i could define 5
pinpoints as functions


void PreWindowPinpoint()
{
MakeDpiAware();
}
void PostWindowPinpoint()
{
timeBeginPeriod(1);

sys_text(0,0,0xffffff,"");

if(initialize_callback)
initialize_callback();


}

void PreFramePinpoint()
{
UpdateKeyboard();


}

void PostFramePinpoint()
{
UpdateFrameGraph();
if(!frame_number%20) UpdateMemoryUsage();
if(f1_toggler) DrawDiagnosticHud();
}

void PostLifePinpoint()
{
timeEndPeriod(1);

}

pre window post window, 2 in frame, and one after all


its still a mess, (i dont know maybe i chosen it wrong, defined it just
now), without it - as places of code its also a mess though , think
maybe even bigger

maybe not guarantee that pinpoints as language mechanism would mend it
but maybe could help


at leastthe non here side become cleaner





void MainLoop()
{

double prev_frame_begin = GetTimeMs();

MSG msg;

for(;;)
{

double current_frame_begin = GetTimeMs();
last_frame_time = (float)(current_frame_begin-prev_frame_begin);
prev_frame_begin = current_frame_begin;

//EVENTS
if(app_minimized)
{
GetMessage(&msg, 0, 0, 0); if(msg.message == WM_QUIT) return;
TranslateMessage(&msg); DispatchMessage(&msg);
continue;
}

while(PeekMessage(&msg, 0, 0, 0, PM_REMOVE))
{
if(msg.message == WM_QUIT) return;
TranslateMessage(&msg); DispatchMessage(&msg);
}



// RUN

PreFramePinpoint(); // <--

double strict_begin = GetTimeMs();
if(runframe_callback) runframe_callback();
double strict_end = GetTimeMs();
last_frame_time_strict = (float)(strict_end-strict_begin);

PostFramePinpoint(); //<---

// BLIT

BlitFrame();

// SLEEP
if(!f2_pressed) Sleep(sleep_value);

//REPEAT
frame_number++;
}
}


--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

bart pisze:

On 27/09/2026 10:54, fir wrote:

i was talking on that recently but now i making some cleaning in my
green fire library i watch on things after rethinking that concept
and yet more see an urging need of this pinpoints in c

without it is really a mess

two examples

1) i got a code that measures usage of ram of my app (as i like to see
it on screen)-a-a and of course i got a function for it in my windows_ut
file.. (which is ok) i draw it in my diagnostic_hud file (also ok)
but i also need a point where i call it (to change how often i call it
(i dont acll it every frame but once some n frames) - and this is NOT
okay


its not okay as i must damn find it thats forst second is i need to
pin many things in this window_setup file but they are not exactly a
part of that file becouse they are only pinned here - need a point to
pin and thet mess of pinned clien is a mes that dont belong to
windows_setup file

it needs to be emphasised and it is more and more clear..

c needs a pin points

whet more pin points are importat to be reckognized in programmer
consciousnes becouse in present state of things it is what makes
or may make some trouble

2) if yu work with ai ai give pices of code but te trouble is often
related to lack of pinpoints becouse you would take the pice and
put it in where you need to put it if you would have pin points defined
you could just replace old separate block and pinpoints would hold

What the hell is a 'pinpoint'? Do you mean literally like a pin you
stick in a map?

If so, then why does it need to be part of the language? This would be
up to your development environment.

C already has the means to inject metadata within source code that can
be detected by some external tool, for example:

-a /* pinpoint(...) */

i explained what it is quite well..you need to read what i wrote

in very short... there are pices f code when you need to attach
other code just becouse they need to di siething in about this place in
code - for example in initialisation place (or initialisation time)

t those special places of code you should have acces from client side i
mean from thiose local pieces not from the "main tree"

i call it pinpoints and you need it in c
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

On 27/09/2026 10:54, fir wrote:

i was talking on that recently but now i making some cleaning in my
green fire library i watch on things after rethinking that concept
and yet more see an urging need of this pinpoints in c

without it is really a mess

two examples

1) i got a code that measures usage of ram of my app (as i like to see
it on screen)-a-a and of course i got a function for it in my windows_ut file.. (which is ok) i draw it in my diagnostic_hud file (also ok)
but i also need a point where i call it (to change how often i call it
(i dont acll it every frame but once some n frames) - and this is NOT
okay

its not okay as i must damn find it thats forst second is i need to
pin many things in this window_setup file but they are not exactly a
part of that file becouse they are only pinned here - need a point to
pin and thet mess of pinned clien is a mes that dont belong to
windows_setup file

it needs to be emphasised and it is more and more clear..

c needs a pin points

whet more pin points are importat to be reckognized in programmer consciousnes becouse in present state of things it is what makes
or may make some trouble

2) if yu work with ai ai give pices of code but te trouble is often
related to lack of pinpoints becouse you would take the pice and
put it in where you need to put it if you would have pin points defined
you could just replace old separate block and pinpoints would hold

What the hell is a 'pinpoint'? Do you mean literally like a pin you
stick in a map?

If so, then why does it need to be part of the language? This would be
up to your development environment.

C already has the means to inject metadata within source code that can
be detected by some external tool, for example:

/* pinpoint(...) */
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

On 2026-09-27, fir wrote:

[...]

c needs a pin points

What is a "pin point"? Nothing you said actually describes what this
"pin point" is, or what it should actually do.

The closest I could fathom was that you want an IDE that allows you to
create something roughly equivalent to HTML anchors...
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

Dan Purgert pisze:

On 2026-09-27, fir wrote:

[...]

c needs a pin points

What is a "pin point"? Nothing you said actually describes what this
"pin point" is, or what it should actually do.

The closest I could fathom was that you want an IDE that allows you to
create something roughly equivalent to HTML anchors...

no there are special places of code when you need to "pin" your code

for exampla i have fsin fcos fatan2 functions
(f stand for fast) which use precomputed lookup tables

so i have some function like

InitOrecomputedFTrigTables()
{
//........
}

ad i nit to pin it at aplication ninitialisation place

to spare
1) extremally tedious code jumping
2) unusual mess in that kind of points like init place

c need pinpoint support like


InitOrecomputedFTrigTables() @init
{
//........
}

where init is just label like this for goto


init:

in some place of code

You need such pinpoint support in c to spare code jumping and
increase code independency and less mess
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

fir pisze:

Dan Purgert pisze:

On 2026-09-27, fir wrote:

[...]

c needs a pin points

What is a "pin point"?-a Nothing you said actually describes what this
"pin point" is, or what it should actually do.

The closest I could fathom was that you want an IDE that allows you to
create something roughly equivalent to HTML anchors...

no there are special places of code when you need to "pin" your code

for exampla i have fsin fcos fatan2 functions
(f stand for fast) which use precomputed lookup tables

so i have some function like

InitOrecomputedFTrigTables()
{
//........
}

ad i nit to pin it at aplication ninitialisation place

to spare
1) extremally tedious code jumping
2) unusual mess in that kind of points like init place

c need pinpoint support like

InitOrecomputedFTrigTables() @init
{
//........
}

where init is just label like this for goto

init:

in some place of code

You need such pinpoint support in c to spare code jumping and
increase code-a independency and less mess

you may have it in points

1. "code independency"
2. "less mess"
3. spare "code jumping"



--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

fir pisze:

fir pisze:

Dan Purgert pisze:

On 2026-09-27, fir wrote:

[...]

c needs a pin points

What is a "pin point"?-a Nothing you said actually describes what this
"pin point" is, or what it should actually do.

The closest I could fathom was that you want an IDE that allows you to
create something roughly equivalent to HTML anchors...

no there are special places of code when you need to "pin" your code

for exampla i have fsin fcos fatan2 functions
(f stand for fast) which use precomputed lookup tables

so i have some function like

InitOrecomputedFTrigTables()
{
//........
}

ad i nit to pin it at aplication ninitialisation place

to spare
1) extremally tedious code jumping
2) unusual mess in that kind of points like init place

c need pinpoint support like


InitOrecomputedFTrigTables() @init
{
//........
}

where init is just label like this for goto


init:

in some place of code

You need such pinpoint support in c to spare code jumping and
increase code-a independency and less mess

you may have it in points

1. "code independency"
2. "less mess"
3. spare "code jumping"

the mechanism is ismple

main
{
init:

for(;;)
{
loop:
}

}
exit:
}

foo() @init {printf("initializing..");}
boo() @init {SetupFont("lucida");}
moo() @exit {DestroyFont("lucida");}

it will compile like

foo() {printf("initializing..");}
boo() {SetupFont("lucida");}
moo() {DestroyFont("lucida");}

main
{
init:
foo();
boo();

for(;;)
{
loop:
}

}
exit:
moo();
}


its not to use all functions this 'reversed' way..but in some crucial
cases you really need it

LIKE you write separate pice of code and as this pice is separate the
points where this piece is "anchored" to main code belong to THIS piece
of code - TO READ IT PROPERLY ypu need only read this piece of code and
know what goven pinpoints mean

this way the architecturally crucial points of "anchor" become able to
be read..in present situation you need to search tru whole tree which is hopeless

this as to independency

you also spare code jumping which is extremally distracting

you know you for example need to anchor your init_tables()
function at app startup point so you only type @init or maybe @app_initialisation no need to travel there and write init_tables()
there

(this is as to spare code jumping)












--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

fir pisze:

fir pisze:

fir pisze:

Dan Purgert pisze:

On 2026-09-27, fir wrote:

[...]

c needs a pin points

What is a "pin point"?-a Nothing you said actually describes what this >>>> "pin point" is, or what it should actually do.

The closest I could fathom was that you want an IDE that allows you to >>>> create something roughly equivalent to HTML anchors...

no there are special places of code when you need to "pin" your code

for exampla i have fsin fcos fatan2 functions
(f stand for fast) which use precomputed lookup tables

so i have some function like

InitOrecomputedFTrigTables()
{
//........
}

ad i nit to pin it at aplication ninitialisation place

to spare
1) extremally tedious code jumping
2) unusual mess in that kind of points like init place

c need pinpoint support like


InitOrecomputedFTrigTables() @init
{
//........
}

where init is just label like this for goto


init:

in some place of code

You need such pinpoint support in c to spare code jumping and
increase code-a independency and less mess

you may have it in points

1. "code independency"
2. "less mess"
3. spare "code jumping"


the mechanism is ismple

main
{
init:

-a for(;;)
-a{
loop:
-a-a-a-a}

}
-aexit:
}

foo() @init {printf("initializing..");}
boo() @init {SetupFont("lucida");}
moo() @exit {DestroyFont("lucida");}

it will compile like

foo() {printf("initializing..");}
boo()-a {SetupFont("lucida");}
moo() {DestroyFont("lucida");}

main
{
init:
-a foo();
-a boo();

-a for(;;)
-a{
loop:
-a-a-a-a}

}
-aexit:
-a moo();
}

its not to use all functions this 'reversed' way..but in some crucial
cases you really need it

LIKE you write separate pice of code and as this pice is separate the
points where this piece is "anchored" to main code belong to THIS piece
of code - TO READ IT PROPERLY ypu need only read this piece of code and
know what goven pinpoints mean

this way the architecturally crucial points of "anchor" become able to
be read..in present situation you need to search tru whole tree which is hopeless

this as to independency

you also spare code jumping which is extremally distracting

you know you for example need to anchor your init_tables()
function at app startup point so you only type @init or maybe @app_initialisation no need to travel there and write init_tables()
there

(this is as to spare code jumping)

some could say i should pin calls not definitions so

@init foo(1,1);


but im not saying here on syntax ofr it yet i more say about abstract
pinpoint concept and why its very much needed










--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

On 2026-09-29, fir wrote:

Dan Purgert pisze:

On 2026-09-27, fir wrote:

[...]

c needs a pin points

What is a "pin point"? Nothing you said actually describes what this
"pin point" is, or what it should actually do.

The closest I could fathom was that you want an IDE that allows you to
create something roughly equivalent to HTML anchors...

no there are special places of code when you need to "pin" your code

for exampla i have fsin fcos fatan2 functions
(f stand for fast) which use precomputed lookup tables

so i have some function like

InitOrecomputedFTrigTables()
{
//........
}

ad i nit to pin it at aplication ninitialisation place

to spare
1) extremally tedious code jumping
2) unusual mess in that kind of points like init place

c need pinpoint support like

InitOrecomputedFTrigTables() @init
{
//........
}

where init is just label like this for goto

init:

in some place of code

You need such pinpoint support in c to spare code jumping and
increase code independency and less mess

Not really sure how this solves anything, you're still going to be
"jumping all over the place" to find those subroutines in the first
place ...
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

On 2026-09-29, fir wrote:

fir pisze:

fir pisze:

Dan Purgert pisze:

On 2026-09-27, fir wrote:

[...]

c needs a pin points

What is a "pin point"?-a Nothing you said actually describes what this >>>> "pin point" is, or what it should actually do.

The closest I could fathom was that you want an IDE that allows you to >>>> create something roughly equivalent to HTML anchors...

no there are special places of code when you need to "pin" your code

for exampla i have fsin fcos fatan2 functions
(f stand for fast) which use precomputed lookup tables

so i have some function like

InitOrecomputedFTrigTables()
{
//........
}

ad i nit to pin it at aplication ninitialisation place

to spare
1) extremally tedious code jumping
2) unusual mess in that kind of points like init place

c need pinpoint support like


InitOrecomputedFTrigTables() @init
{
//........
}

where init is just label like this for goto


init:

in some place of code

You need such pinpoint support in c to spare code jumping and
increase code-a independency and less mess

you may have it in points

1. "code independency"
2. "less mess"
3. spare "code jumping"


the mechanism is ismple

main
{
init:

for(;;)
{
loop:
}

}
exit:
}
[...]
its not to use all functions this 'reversed' way..but in some crucial
cases you really need it

Let's say you're looking at the 'init:' anchor up there. What's getting called?

How do you know without "jumping all over the code" ?
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

On 30/09/2026 23:32, Dan Purgert wrote:

On 2026-09-29, fir wrote:

Dan Purgert pisze:

On 2026-09-27, fir wrote:

[...]

c needs a pin points

What is a "pin point"? Nothing you said actually describes what this
"pin point" is, or what it should actually do.

The closest I could fathom was that you want an IDE that allows you to
create something roughly equivalent to HTML anchors...

no there are special places of code when you need to "pin" your code

for exampla i have fsin fcos fatan2 functions
(f stand for fast) which use precomputed lookup tables

so i have some function like

InitOrecomputedFTrigTables()
{
//........
}

ad i nit to pin it at aplication ninitialisation place

to spare
1) extremally tedious code jumping
2) unusual mess in that kind of points like init place

c need pinpoint support like


InitOrecomputedFTrigTables() @init
{
//........
}

where init is just label like this for goto


init:

in some place of code

You need such pinpoint support in c to spare code jumping and
increase code independency and less mess

Not really sure how this solves anything, you're still going to be
"jumping all over the place" to find those subroutines in the first
place ...

The concept of being able to write code that is implicitly run before
main() is common in many languages. Pascal units have their initialiser
code, C++ constructors and initialisers for program-lifetime objects run before main(), and gcc has the "constructor" attribute as an extension.

The benefit of this is primarily for being able to put such code in a
very different place than "main()" - it's strange to see Fir's example
of "init::" inside main() in another post.

And I think it is inevitable that it would mean "jumping all over the
place" - with the pros and cons that brings.


--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

Dan Purgert pisze:

On 2026-09-29, fir wrote:

fir pisze:

fir pisze:

Dan Purgert pisze:

On 2026-09-27, fir wrote:

[...]

c needs a pin points

What is a "pin point"?-a Nothing you said actually describes what this >>>>> "pin point" is, or what it should actually do.

The closest I could fathom was that you want an IDE that allows you to >>>>> create something roughly equivalent to HTML anchors...

no there are special places of code when you need to "pin" your code

for exampla i have fsin fcos fatan2 functions
(f stand for fast) which use precomputed lookup tables

so i have some function like

InitOrecomputedFTrigTables()
{
//........
}

ad i nit to pin it at aplication ninitialisation place

to spare
1) extremally tedious code jumping
2) unusual mess in that kind of points like init place

c need pinpoint support like


InitOrecomputedFTrigTables() @init
{
//........
}

where init is just label like this for goto


init:

in some place of code

You need such pinpoint support in c to spare code jumping and
increase code-a independency and less mess

you may have it in points

1. "code independency"
2. "less mess"
3. spare "code jumping"


the mechanism is ismple

main
{
init:

for(;;)
{
loop:
}

}
exit:
}
[...]
its not to use all functions this 'reversed' way..but in some crucial
cases you really need it

Let's say you're looking at the 'init:' anchor up there. What's getting called?

How do you know without "jumping all over the code" ?

when developing the program you usually write a modules (files of code)
that you later pin

so you have such module open than you dont jump on code if you use thi s syntax on remote pin

note the modules have usualy like 3 inpoints each not just one


in the other scenartio you write five modules you got a lot of jumping

it is not only on jumping hovever as i said..its also on architecture


i began to artificially denote pinpoints as a functions - it more
clearly shows thise pinpoints - how the modules are wired/sewed and
in what points


see those pinpoints its a mess but those pinpoints are generally a mess
and naming them helps


void PreWindowPinpoint()
{
MakeDpiAware();

InitOPtiTables();

SetupRawInput();
}


void PreLoopPinpoint()
{
timeBeginPeriod(1);

// sys_text(0,0,0xffffff,"");

if(initialize_callback) initialize_callback();
}


void PreFramePinpoint()
{
UpdateKeyboard();

if(arrow_hidden) CenterCursor();

}


void PostFramePinpoint()
{
UpdateFrameGraph();

if(!(frame_number%20)) UpdateMemoryUsage();

if(f1_toggler) DrawDiagnosticHud();

raw_mouse_dx = 0;
raw_mouse_dy = 0;

}


void PostLifePinpoint()
{
timeEndPeriod(1);
}


(some i could name like

keyboard_pin() {UpdateKeyboard();}

and only put this name in that pinpoint

PreFramePinpoint()
{
keyboard_pin();
}

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

David Brown pisze:

On 30/09/2026 23:32, Dan Purgert wrote:

On 2026-09-29, fir wrote:

Dan Purgert pisze:

On 2026-09-27, fir wrote:

[...]

c needs a pin points

What is a "pin point"?-a Nothing you said actually describes what this >>>> "pin point" is, or what it should actually do.

The closest I could fathom was that you want an IDE that allows you to >>>> create something roughly equivalent to HTML anchors...

no there are special places of code when you need to "pin" your code

for exampla i have fsin fcos fatan2 functions
(f stand for fast) which use precomputed lookup tables

so i have some function like

InitOrecomputedFTrigTables()
{
//........
}

ad i nit to pin it at aplication ninitialisation place

to spare
1) extremally tedious code jumping
2) unusual mess in that kind of points like init place

c need pinpoint support like


InitOrecomputedFTrigTables() @init
{
//........
}

where init is just label like this for goto


init:

in some place of code

You need such pinpoint support in c to spare code jumping and
increase code-a independency and less mess

Not really sure how this solves anything, you're still going to be
"jumping all over the place" to find those subroutines in the first
place ...

The concept of being able to write code that is implicitly run before
main() is common in many languages.-a Pascal units have their initialiser code, C++ constructors and initialisers for program-lifetime objects run before main(), and gcc has the "constructor" attribute as an extension.

The benefit of this is primarily for being able to put such code in a
very different place than "main()" - it's strange to see Fir's example
of "init::" inside main() in another post.

And I think it is inevitable that it would mean "jumping all over the
place" - with the pros and cons that brings.

its not quite concept of being able (....) becouse those pinpoints work
at compile time as you should notice

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

Dan Purgert pisze:

On 2026-09-29, fir wrote:

Dan Purgert pisze:

On 2026-09-27, fir wrote:

[...]

c needs a pin points

What is a "pin point"? Nothing you said actually describes what this
"pin point" is, or what it should actually do.

The closest I could fathom was that you want an IDE that allows you to
create something roughly equivalent to HTML anchors...

no there are special places of code when you need to "pin" your code

for exampla i have fsin fcos fatan2 functions
(f stand for fast) which use precomputed lookup tables

so i have some function like

InitOrecomputedFTrigTables()
{
//........
}

ad i nit to pin it at aplication ninitialisation place

to spare
1) extremally tedious code jumping
2) unusual mess in that kind of points like init place

c need pinpoint support like


InitOrecomputedFTrigTables() @init
{
//........
}

where init is just label like this for goto


init:

in some place of code

You need such pinpoint support in c to spare code jumping and
increase code independency and less mess

Not really sure how this solves anything, you're still going to be
"jumping all over the place" to find those subroutines in the first
place ...

you would need a bit deeper to rethink it and you would see it

i would seay with no pinpoints (or some analogy of it maybe) there is no
code architecture at all - so for example this oop is hoax

becouse you need to show those architectural points some way

keeping them inside modules is at least some way

not saing this is best possible (becouse still thise pinpoint seem a bit vague) but better than nothing

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

fir pisze:

Dan Purgert pisze:

On 2026-09-29, fir wrote:

fir pisze:

fir pisze:

Dan Purgert pisze:

On 2026-09-27, fir wrote:

[...]

c needs a pin points

What is a "pin point"?-a Nothing you said actually describes what this >>>>>> "pin point" is, or what it should actually do.

The closest I could fathom was that you want an IDE that allows
you to
create something roughly equivalent to HTML anchors...

no there are special places of code when you need to "pin" your code >>>>>
for exampla i have fsin fcos fatan2 functions
(f stand for fast) which use precomputed lookup tables

so i have some function like

InitOrecomputedFTrigTables()
{
//........
}

ad i nit to pin it at aplication ninitialisation place

to spare
1) extremally tedious code jumping
2) unusual mess in that kind of points like init place

c need pinpoint support like


InitOrecomputedFTrigTables() @init
{
//........
}

where init is just label like this for goto


init:

in some place of code

You need such pinpoint support in c to spare code jumping and
increase code-a independency and less mess

you may have it in points

1. "code independency"
2. "less mess"
3. spare "code jumping"


the mechanism is ismple

main
{
init:

-a-a-a for(;;)
-a-a {
loop:
-a-a-a-a}

}
-a-a exit:
}
[...]
its not to use all functions this 'reversed' way..but in some crucial
cases you really need it

Let's say you're looking at the 'init:' anchor up there.-a What's
getting called?

How do you know without "jumping all over the code" ?

when developing the program you usually write a modules (files of code)
that you later pin

so you have such module open than you dont jump on code if you use thi s syntax on remote pin

note the modules have usualy like 3 inpoints each not just one

in the other scenartio you write five modules you got a lot of jumping

it is not only on jumping hovever as i said..its also on architecture

i began to artificially denote pinpoints as a functions - it more
clearly shows thise pinpoints - how the modules are wired/sewed and
in what points

see those pinpoints its a mess but those pinpoints are generally a mess
and naming them helps

void PreWindowPinpoint()
{
-a-a-a-aMakeDpiAware();

-a-a-a-aInitOPtiTables();

-a-a-a-aSetupRawInput();
}

void PreLoopPinpoint()
{
-a-a-a-atimeBeginPeriod(1);

//-a-a-a sys_text(0,0,0xffffff,"");

-a-a-a-aif(initialize_callback) initialize_callback();
}

void PreFramePinpoint()
{
-a-a-a-aUpdateKeyboard();

-a-a-a-aif(arrow_hidden) CenterCursor();

}

void PostFramePinpoint()
{
-a-a-a-aUpdateFrameGraph();

-a-a-a-aif(!(frame_number%20)) UpdateMemoryUsage();

-a-a-a-aif(f1_toggler) DrawDiagnosticHud();

-a-a-a-araw_mouse_dx = 0;
-a-a-a-a raw_mouse_dy = 0;

}

void PostLifePinpoint()
{
-a-a-a-atimeEndPeriod(1);
}

-a(some i could name like

keyboard_pin() {UpdateKeyboard();}

and only put this name in that pinpoint

PreFramePinpoint()
{
-a-a keyboard_pin();
}

i got no practice in simulating of this pinpoints in c so i dont know
which is best now rewritten my 5 pinpoint to


void PreWindow__Pinpoint()
{

Util_PreWindow_pin(); //generate tables for cosin & atan
Input_PreWindow_pin(); //setup raw input
}


void PostWindow__Pinpoint()
{

}


void PreFrame__Pinpoint()
{
Input_PreFrame_pin(); //setup keys variables

if(arrow_hidden) CenterCursor(); // ???

}


void PostFrame__Pinpoint()
{

DiagnosticHud_PostFrame_pin(); //update and draw
Input_PostFrame_pin(); // zero mouse variables
}


void PostLife__Pinpoint()
{

}



only 3 used - yet one used is WNdProc__Pinpoint() which i yet
not defined but it need to be defined


generally in app you got limited number of pinpoints imo

yet ypu may call on the "trunk" side and modules side as imo you
generally pin modules to the truunk of code... though in more alaborated
apps probably those could be more of this pinpoints too

this above is far from ideal but at least on abstract way for me its
celar pinpoints or some analog of it is absolutely neded
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.lang.c

fir pisze:

fir pisze:

Dan Purgert pisze:

On 2026-09-29, fir wrote:

fir pisze:

fir pisze:

Dan Purgert pisze:

On 2026-09-27, fir wrote:

[...]

c needs a pin points

What is a "pin point"?-a Nothing you said actually describes what >>>>>>> this
"pin point" is, or what it should actually do.

The closest I could fathom was that you want an IDE that allows >>>>>>> you to
create something roughly equivalent to HTML anchors...

no there are special places of code when you need to "pin" your code >>>>>>
for exampla i have fsin fcos fatan2 functions
(f stand for fast) which use precomputed lookup tables

so i have some function like

InitOrecomputedFTrigTables()
{
//........
}

ad i nit to pin it at aplication ninitialisation place

to spare
1) extremally tedious code jumping
2) unusual mess in that kind of points like init place

c need pinpoint support like


InitOrecomputedFTrigTables() @init
{
//........
}

where init is just label like this for goto


init:

in some place of code

You need such pinpoint support in c to spare code jumping and
increase code-a independency and less mess

you may have it in points

1. "code independency"
2. "less mess"
3. spare "code jumping"


the mechanism is ismple

main
{
init:

-a-a-a for(;;)
-a-a {
loop:
-a-a-a-a}

}
-a-a exit:
}
[...]
its not to use all functions this 'reversed' way..but in some crucial
cases you really need it

Let's say you're looking at the 'init:' anchor up there.-a What's
getting called?

How do you know without "jumping all over the code" ?

when developing the program you usually write a modules (files of code)
that you later pin

so you have such module open than you dont jump on code if you use thi
s syntax on remote pin

note the modules have usualy like 3 inpoints each not just one


in the other scenartio you write five modules you got a lot of jumping

it is not only on jumping hovever as i said..its also on architecture


i began to artificially denote pinpoints as a functions - it more
clearly shows thise pinpoints - how the modules are wired/sewed and
in what points


see those pinpoints its a mess but those pinpoints are generally a mess
and naming them helps


void PreWindowPinpoint()
{
-a-a-a-a-aMakeDpiAware();

-a-a-a-a-aInitOPtiTables();

-a-a-a-a-aSetupRawInput();
}


void PreLoopPinpoint()
{
-a-a-a-a-atimeBeginPeriod(1);

//-a-a-a sys_text(0,0,0xffffff,"");

-a-a-a-a-aif(initialize_callback) initialize_callback();
}


void PreFramePinpoint()
{
-a-a-a-a-aUpdateKeyboard();

-a-a-a-a-aif(arrow_hidden) CenterCursor();

}


void PostFramePinpoint()
{
-a-a-a-a-aUpdateFrameGraph();

-a-a-a-a-aif(!(frame_number%20)) UpdateMemoryUsage();

-a-a-a-a-aif(f1_toggler) DrawDiagnosticHud();

-a-a-a-a-araw_mouse_dx = 0;
-a-a-a-a-a raw_mouse_dy = 0;

}


void PostLifePinpoint()
{
-a-a-a-a-atimeEndPeriod(1);
}


-a-a(some i could name like

keyboard_pin() {UpdateKeyboard();}

and only put this name in that pinpoint

PreFramePinpoint()
{
-a-a-a keyboard_pin();
}

i got no practice in simulating of this pinpoints in c so i dont know
which is best now rewritten my 5 pinpoint to

void PreWindow__Pinpoint()
{

-a-a-a-aUtil_PreWindow_pin(); //generate tables for cosin & atan
-a-a-a-aInput_PreWindow_pin(); //setup raw input
}

void PostWindow__Pinpoint()
{

}

void PreFrame__Pinpoint()
{
-a-a-a-aInput_PreFrame_pin(); //setup keys variables

-a-a-a-aif(arrow_hidden) CenterCursor(); // ???

}

void PostFrame__Pinpoint()
{

-a-a-a-aDiagnosticHud_PostFrame_pin(); //update and draw
-a-a-a-aInput_PostFrame_pin();-a-a-a // zero mouse variables
}

note this elaborate "simulation" way is troublesome...it would
be better imo only pin it on module side (and do not write this pair
of addidtional boilerplate function names)

you say say you define those call now on trunk side , then you
would define that on module size so instead of jumping to trounk you
need to jump to module - BUT as i said (but repeat yet once)
you usually work on given module (code pice) when you develop it and
if youre in this pice of code than yu spare a jumping and this is most important imo... it is also a fact that the pin BELONGS to module as
this is a pice of code of module that you pin, and the code is module code..the trunk code is trunk code


overally those sewing things are problematic and there is some scent
of 60ties "goto hell" troubles here imo - becouse when you pin things
its not very clear on what state of things operate - so its not clear
there is some deeper problem here, but pinpoints may help to pin that
problem maybe imo

(maybe also winapi makes some problems here as - winapi host thsi
unpleasant hidden states

void PostLife__Pinpoint()
{

}

only 3 used - yet one used is WNdProc__Pinpoint() which i yet
not defined but it need to be defined

generally in app you got limited number of pinpoints imo

yet ypu may call on the "trunk" side and modules side as imo you
generally pin modules to the truunk of code... though in more alaborated apps probably those could be more of this pinpoints too

this above is far from ideal but at least on abstract way for me its
celar pinpoints or some analog of it is absolutely neded

--- Synchronet 3.22a-Linux NewsLink 1.2