I've finally added a function to output floats (in scientific notation):
> 355 s>f 113 s>f f/ fs.
3.1415927 ok
> 1 s>f f2/ f2/ f2/ f2/ fs.
6.25E-2 ok
> 12345 s>f fs.
1.23449993E4 ok
You can see from the second example that rounding problems do happen. That can
be avoided... if you don't mind
If I have to choose between "fast" or "ugly" then case sensitive being
fast and beautiful it is.
If I went with personal convenience and C# et al I would be running
windows and certainly wouldn't be contributing to Open Source.
Come up with a reasoned argument (other than personal convenience) th
The timer routine with automated tck_ms (float) calculation (I had
to test the tck_ms calculation a little bit..):
...
\ MEASURE TIME IN SECONDS (FLOAT)
decimal
2variable elapsed_ticks
\ tck_ms = 1 / f_cpu / timer2_overflow_count /
timer2_prescaler_ratio
\ tck_ms = 1 / f_cpu / 256 / 1024
f_cpu d>f
So can we see light at the end of the tunnel? (hopefuly it's not the
light of an incoming train..). Have a nice weekend! P.
>
> I want a smart solution, not a fast and ugly one.
> And smart means
> really smart. And I take the time for it... I've
> got some ideas
> already...
>
> Matthias
Pito,
> I do understand the issue with comparing words and not single chars
> in you implementation, but tell me please - what is the major reason
> for your hardcore position of not wanting to have a switch for case
> sensitivity/insensitivity?
I want a smart solution, not a fast and ugly one. A
Matthias,
yes, sometimes I never give up..
I do understand the issue with comparing words and not single chars
in you implementation, but tell me please - what is the major reason
for your hardcore position of not wanting to have a switch for case
sensitivity/insensitivity? Pito
...
(besides that
Pito,
you never give, yea?
> the 4th is using a constant "casesensitive" for switching case
> sensitivity on/off. I've found that only "compare.4th" is using this
> constant (compares two strings). In C sources there is "comp_4th.c"
> which does mention sensitivness, but not using the constant. C
Hi, for experimenters - very quick test for floating point math with
elapsed time indication. Requires Leon's float lib, Pito's last
floatconstants and stopwatch. To see result uncomment print.
Benchmark (run on atmega1284P @25MHz):
> measure_doloop_with_operation
Elapsed 8996 msec ok
> Pito
\ Qui
The last update:
-
marker _floatconstants_
\ some float constants
355 s>f 113 s>f f/ fconstant_pi
355 s>f 226 s>f f/ fconstant_pi_half
355 s>f 452 s>f f/ fconstant_pi_quarter
8119 s>f 5741 s>f f/ fconstant _sqrt2
5741 s>f 8
Hi Matthias,
the 4th is using a constant "casesensitive" for switching case
sensitivity on/off. I've found that only "compare.4th" is using this
constant (compares two strings). In C sources there is "comp_4th.c"
which does mention sensitivness, but not using the constant. Can
this somehow be used
10 matches
Mail list logo
