i wonder if to not began to use

typedef int I; typedef float F; typedef char C; typedef long long L;

i never to used this but recently i noticed i get more advanced in c
and more not plain, more cryptic codes that are shorter become better
to me... it is change in philosophy but it seem right

the adwantage is that in fact its a spare of lot typilg
as big I or big F are very short to type (easier than + or *)

so is it right or wrong decision? (in fact its hard to judge without
longer use it in practicem, but phylosphically it may be good)

(soem noobs may think its weird code though, but im not
in respect with ponys to much; worse hovever it would be if its
from some aspects not so much bad decision)

one big disadvantage is that my editor colorises int float in different colors than function and variables and here thic separata color is lost)

środa, 16 sierpnia 2023 o 23:55:05 UTC+2 fir napisał(a):
> i wonder if to not began to use
>
> typedef int I; typedef float F; typedef char C; typedef long long L;
>
> i never to used this but recently i noticed i get more advanced in c
> and more not plain, more cryptic codes that are shorter become better
> to me... it is change in philosophy but it seem right
>
> the adwantage is that in fact its a spare of lot typilg
> as big I or big F are very short to type (easier than + or *)
>
> so is it right or wrong decision? (in fact its hard to judge without
> longer use it in practicem, but phylosphically it may be good)
>
> (soem noobs may think its weird code though, but im not
> in respect with ponys to much; worse hovever it would be if its
> from some aspects not so much bad decision)
>
> one big disadvantage is that my editor colorises int float in different colors than function and variables and here thic separata color is lost)

other disadvantage is it looks slightly weird - not that i disliked code that uses int,float,
those show cleanly what it is, but the question is if code needs to show cleanly what i cleanly know