[sdiy] large numbers

[sleepy_dog at gmx.de]

Tom Wiltshire wrote:
> People, we’re only trying to spit out a look-up table here, not decide “what’s the best programming language?”
>
> Basically anything would do the job; BASIC, Python, PHP, Excel, Perl, whatever. You could do it in Javascript if you could be bothered. I wouldn’t particularly like to try it in Prolog though.

Oh my, are we running astray again, eh? The topic seems to have been 
solved more or less I guess, though.

Prolog is a quite funny language though. I remember implementing some 
tree searching stuff in it for fun, to see it works, long time ago, though.
It would be a really cool language if the order of statements separated 
by comma did NOT matter, though. It's kind of a bummer that it does, 
kind of a breach of the principle that otherwise seems to emerge (or I 
would like to see), don't have a word for it right now.
Declarative stuff is kinda cool.

>
>> On 15 Jul 2018, at 09:58, sleepy_dog at gmx.de wrote:
>>
>> Michael E Caloroso wrote:
>>> I inherited a system at work that uses Python.
>>>
>>> I've been building and maintaining systems for 25+ years in my career
>>> and in my professional opinion Python is not a very good language.
>> Care to elaborate?
>> Just guessing a few things: Isn't that a "right tool for the job" thing?
>> Some people enjoy it for scientific computing / visualization over Matlab for some scenarios.
>> I guess I wouldn't use it for anything that goes over a lot of data and does computations in python itself, as it's slow as hell. If it's mostly calls to libraries written in C, though...
>> Or anything bigger / complex.
>>
>> For whipping together short scripts that quickly do something for you, it seems to be good. Less verbose than many other languages, rich and expressive, so there are less code blocks and boiler plate code to get something done quickly.
>> I say that from impressions gained watching others use Python, I'm not literate in Python myself and don't like how it looks, and am generally skeptical of (the merit of) dynamic typing (as such, not things often falsely attributed as exclusive, defining characteristics of dynamic languages).
>>
>>
>> - Steve
>>
>>
>>> MC
>>>
>>> On 7/14/18, ASSI <Stromeko at nexgo.de> wrote:
>>>> On Friday, July 13, 2018 8:33:42 PM CEST Tim Ressel wrote:
>>>>> I am playing with using a 64 bit accumulator in a DCO (NCO?) to fix the
>>>>> top jitter problem. The notion is that increased resolution in the
>>>>> increment value will cause less top jitter.
>>>> In that particular case, you are most certainly trying to solve the wrong
>>>> problem (increasing the resolution of the phase accumulator beyond
>>>> reasonable)
>>>> using the wrong tool (Excel, which uses double floating point numbers, so
>>>> 53bits of mantissa)  …unless you've somehow figured out how to run your NCO
>>>> at
>>>> several dozen GHz.
>>>>
>>>>
>>>> Regards,
>>>> Achim.
>>>> --
>>>> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>>>>
>>>> Factory and User Sound Singles for Waldorf Blofeld:
>>>> http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Synth-diy mailing list
>>>> Synth-diy at synth-diy.org
>>>> http://synth-diy.org/mailman/listinfo/synth-diy
>>>>
>>> _______________________________________________
>>> Synth-diy mailing list
>>> Synth-diy at synth-diy.org
>>> http://synth-diy.org/mailman/listinfo/synth-diy
>>
>> _______________________________________________
>> Synth-diy mailing list
>> Synth-diy at synth-diy.org
>> http://synth-diy.org/mailman/listinfo/synth-diy
>
> _______________________________________________
> Synth-diy mailing list
> Synth-diy at synth-diy.org
> http://synth-diy.org/mailman/listinfo/synth-diy