Re: Multimeter USB output
Am 30.08.2016 um 06:24 schrieb Paul Rubin: Larry Hudson writes: with BDS-C under CP/M. Somebody remenbering this no-fp compiler from the dark age before PC und Linux? I remember it well. It's what I used to initially learn C. Source code is online here: http://www.bdsoft.com/resources/bdsc.html I've looked at it a little. I don't know if I ever might have had it in me to write big chunks of asm code like that. Wow! Great surprise. Very interesting this link. Thank you, Paul. -- https://mail.python.org/mailman/listinfo/python-list
Re: importing down in code rather than at top of file.
Tobiah writes: > Is it worth while to defer the import of a large module that seldom > gets used in the script? > > > import sys > import os > > if hardly_ever_happens(): > > import large_module > large_module.do_task() I have used delayed import for different reasons: * to avoid cyclical imports * to avoid import deadlocks in multi-tasking programs (Python 2 (at least) used to protect the import machinery with a lock; which under some conditions could lead to deadlocks in a multi-tasking program). Typically, the delayed import was then in a function - relying on the fact that importing an already imported module is fast (thus, we do not lose much even if the function is called multiple times). -- https://mail.python.org/mailman/listinfo/python-list
Re: Helloworld with Python C extension
Am 30.08.16 um 08:06 schrieb Ganesh Pal:
Py_BuildValue with an "s" expects a C string - that is, a pointer to
char, not just a single character. You'd need to do something like
this:
char buf[2] = {char1, 0};
return Py_BuildValue("s", buf);
ChrisA
Thanks Chris for the clue's it worked, I was just wondering how
could the
C extension be debugged ?
We have pdb at python side and gdb for C , can we run gdb on python side
? if there is a crash like the one we saw in the above diff we are
clueless of what's happening? any idea or recommendation on how we handle
such cases
1. Write your Python code into a file (e.g. test.py)
2. Run gdb --args python test.py
Then press "r" to start your program. At the crash, gdb should stop your
program, maybe inside of Py_BuildValue. You must compile your extension
with debug symbols (-g switch to the compiler) enabled to see line numbers.
In case of memory errors like the above, they can sometimes go unnoticed
for a while, which makes them hard to debug. If you are on Linux,
valgrind is the most powerful tool to find these. Run
valgrind python test.py
It'll show out-of-bounds accesses for arrays immediately.
Christian
--
https://mail.python.org/mailman/listinfo/python-list
Re: Magic UTF-8/Windows-1252 encodings
On 29.08.2016 17:59, Chris Angelico wrote: > Fair enough. If this were something that a lot of programs wanted, > then yeah, there'd be good value in stdlibbing it. Character encodings > ARE hard to get right, and this kind of thing does warrant some help. > But I think it's best not done in core - at least, not until we see a > lot more people doing the same :) I hope this kind of botchery never makes it in the stdlib. It directly contradicts "In the face of ambiguity, refuse the temptation to guess." If you don't know what the charset is, don't guess. It'll introduce subtle ambiguities and ugly corner cases and will make the life for the rest of us -- who are trying to get their charsets straight and correct -- a living hell. Having such silly "magic" guessing stuff is actually detrimental to the whole concept of properly identifying and using character sets. Everything about the thought makes me shiver. Cheers, Johannes -- >> Wo hattest Du das Beben nochmal GENAU vorhergesagt? > Zumindest nicht öffentlich! Ah, der neueste und bis heute genialste Streich unsere großen Kosmologen: Die Geheim-Vorhersage. - Karl Kaos über Rüdiger Thomas in dsa -- https://mail.python.org/mailman/listinfo/python-list
Re: Magic UTF-8/Windows-1252 encodings
On Tue, Aug 30, 2016 at 7:36 PM, Johannes Bauer wrote: > On 29.08.2016 17:59, Chris Angelico wrote: > >> Fair enough. If this were something that a lot of programs wanted, >> then yeah, there'd be good value in stdlibbing it. Character encodings >> ARE hard to get right, and this kind of thing does warrant some help. >> But I think it's best not done in core - at least, not until we see a >> lot more people doing the same :) > > I hope this kind of botchery never makes it in the stdlib. It directly > contradicts "In the face of ambiguity, refuse the temptation to guess." > > If you don't know what the charset is, don't guess. It'll introduce > subtle ambiguities and ugly corner cases and will make the life for the > rest of us -- who are trying to get their charsets straight and correct > -- a living hell. > > Having such silly "magic" guessing stuff is actually detrimental to the > whole concept of properly identifying and using character sets. > Everything about the thought makes me shiver. In the clinical purity of theoretical work, I absolutely agree with you, and for that reason, this definitely doesn't belong in the stdlib. But designers need to leave their wonderlands - the real world is not so wonderful. (Nan Sharpe, to Alice Liddell.) If every program in the world understood character encodings and correctly decoded bytes using a known encoding and encoded text using the same encoding (preferably UTF-8), then sure, it'd be easy. But when your program has to cope with other people's bytes-that-ought-to-represent-text, sometimes guessing IS better than choking. This example is a perfect one; a naive byte-oriented server accepts ASCII-compatible text from a variety of clients, and sends it out to all clients. (Since all the parts that the server actually parses are ASCII, this works.) Very commonly, naive Windows clients send text in the native encoding, eg CP-1252, but smarter clients generally send UTF-8. I want my client to interoperate perfectly with other UTF-8 clients, which is generally easy (the only breakage is if the server attempts to letter-wrap a massively long word, and ends up breaking a UTF-8 sequence across lines), but I also want to have a decent fallback for the eight-bit clients. Obviously I can't *know* the encoding used - if they were smart enough to send encoding info, they'd most likely use UTF-8 - so it's either guess, or choke on any non-ASCII bytes. Another place where guessing is VERY useful is when I'm leafing through 300 subtitles files for "Tangled" and want to know whether they're accurate transcriptions or not. (Not hypothetical. Been doing exactly that for a lot of this weekend. It seemed logical, since I've done the same for "Frozen", and both movies are excellent.) All I have is a file - a sequence of bytes. I know it's an ASCII-compatible encoding because the numeric positioning info looks correct. If my program "avoided the temptation to guess", I would have to manually test a dozen encodings until one of them looked right to me, the human; but instead, I use chardet plus some other heuristics, and generally the program's right on either the first or second guess. That means just two encodings for me to look at, often just one, and only going to the full dozen or so if it gets it completely wrong. The principle "refuse the temptation to guess" applies to core data types and such (and not even universally there), but NOT to applications, where you need domain knowledge to make that kind of call. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Itertools Python3
Hi,
I can not write to the file.
Can someone help me?
Thanks
from itertools import product
valore = input('Inserisci un valore: ')
risultato = product(valore, repeat = 3)
with open("file.txt", "w") as result:
for i in risultato:
print (result,"".join(i))
--
https://mail.python.org/mailman/listinfo/python-list
Re: Itertools Python3
On Tue, Aug 30, 2016 at 8:24 PM, Smith wrote:
> I can not write to the file.
> Can someone help me?
> Thanks
>
> from itertools import product
> valore = input('Inserisci un valore: ')
> risultato = product(valore, repeat = 3)
> with open("file.txt", "w") as result:
> for i in risultato:
> print (result,"".join(i))
Do you get an exception, possibly from the product() call? When you
ask for help, copy and paste the entire traceback and error message;
it's extremely useful information.
I'm pretty sure I know what the problem is here, but I want you to
post the traceback, so that you learn how debugging of Python code
works :)
ChrisA
--
https://mail.python.org/mailman/listinfo/python-list
Re: Itertools Python3
Il 30/08/2016 12:28, Chris Angelico ha scritto: Do you get an exception, possibly from the product() call? When you ask for help, copy and paste the entire traceback and error message; it's extremely useful information. I'm pretty sure I know what the problem is here, but I want you to post the traceback, so that you learn how debugging of Python code works python3 toolgen.py Inserisci un valore: dog <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ddd <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ddo <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ddg <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> dod <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> doo <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> dog <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> dgd <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> dgo <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> dgg <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> odd <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> odo <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> odg <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ood <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ooo <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> oog <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ogd <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ogo <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ogg <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> gdd <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> gdo <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> gdg <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> god <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> goo <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> gog <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ggd <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ggo <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ggg -- https://mail.python.org/mailman/listinfo/python-list
Re: Itertools Python3
On Tue, Aug 30, 2016 at 8:45 PM, Smith wrote: > Il 30/08/2016 12:28, Chris Angelico ha scritto: >> >> Do you get an exception, possibly from the product() call? When you >> ask for help, copy and paste the entire traceback and error message; >> it's extremely useful information. >> >> I'm pretty sure I know what the problem is here, but I want you to >> post the traceback, so that you learn how debugging of Python code >> works > > python3 toolgen.py > Inserisci un valore: dog > <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ddd > <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ddo > <_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'> ddg > ... So it's not giving you an exception, just outputting to the screen instead of the file. Okay. Next thing to look into: How does the print function actually get told about a file to output to? You can type help(print) at the interactive prompt, or look in the docs online: https://docs.python.org/3/library/functions.html#print Check how you're using that function, because it doesn't seem to be doing what you expect. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Multimeter USB output
On Mon, 29 Aug 2016 21:21:05 -0700 Larry Hudson via Python-list wrote: > I remember it well. It's what I used to initially learn C. I'm a > completely self-taught, hobby programmer. Been around since the MITS > Altair. How many remember that beast?? Remember it and still have it in the basement. -- D'Arcy J.M. Cain System Administrator, Vex.Net http://www.Vex.Net/ IM:da...@vex.net VoIP: sip:da...@vex.net -- https://mail.python.org/mailman/listinfo/python-list
[CmdTree] sub-command friendly cli library for python : )
Hi there, I'm winkidney:), Recently when I work on a cli auto-generating task, I tryed "click" and "argparse" to handle it. But I have to write a library myself to do this job finally. I wish this library helps you ：） Project Github Repo: https://github.com/winkidney/cmdtree Why CmdTree? Alternatives: click library argparse library But when you should choose cmdtree? If you need: + fully sub-command support(not group in click) + Higher-level api support(compare to argparse) + More arg-type support(compare to argparse) + decorators has no side-effect on function call You may be a proper user of CmdTree Best wishes -- https://mail.python.org/mailman/listinfo/python-list
Re: Itertools Python3
Il 30/08/2016 12:28, Chris Angelico ha scritto:
On Tue, Aug 30, 2016 at 8:24 PM, Smith wrote:
I can not write to the file.
Can someone help me?
Thanks
from itertools import product
valore = input('Inserisci un valore: ')
risultato = product(valore, repeat = 3)
with open("file.txt", "w") as result:
for i in risultato:
print (result,"".join(i))
Do you get an exception, possibly from the product() call? When you
ask for help, copy and paste the entire traceback and error message;
it's extremely useful information.
I'm pretty sure I know what the problem is here, but I want you to
post the traceback, so that you learn how debugging of Python code
works :)
ChrisA
The problem is solved
I thank you for your time
from itertools import product
valore = input('Inserisci un valore: ')
risultato = product(valore, repeat = 3)
with open("file.txt", "w") as result:
for i in risultato:
print ("".join(i),file=result)
--
https://mail.python.org/mailman/listinfo/python-list
Re: Multimeter USB output
Am 30.08.2016 um 13:01 schrieb D'Arcy J.M. Cain: On Mon, 29 Aug 2016 21:21:05 -0700 Larry Hudson via Python-list wrote: I remember it well. It's what I used to initially learn C. I'm a completely self-taught, hobby programmer. Been around since the MITS Altair. How many remember that beast?? Remember it and still have it in the basement. I read a lot about the Altair in Byte in those days, but never had a chance to touch it. Wasn't it horrible expensive? -- https://mail.python.org/mailman/listinfo/python-list
Re: [OT] Altair
On Tue, 30 Aug 2016 15:56:07 +0200 Joe wrote: > Am 30.08.2016 um 13:01 schrieb D'Arcy J.M. Cain: > > On Mon, 29 Aug 2016 21:21:05 -0700 > > Larry Hudson via Python-list wrote: > >> I remember it well. It's what I used to initially learn C. I'm a > >> completely self-taught, hobby programmer. Been around since the > >> MITS Altair. How many remember that beast?? > > > > Remember it and still have it in the basement. > > > I read a lot about the Altair in Byte in those days, but never had a > chance to touch it. Wasn't it horrible expensive? I can't remember what is was going for but I bought mine used for $1,000. It had a number of add-ons including a keyboard and floppy drives. The power supply was also beefed up. It also had a replacement bezel. It seems that the original Altair's silk screened front panel was crappy and rubbed off easily. Some company sold one but it says "Cycloid" instead of "Altair" on it. -- D'Arcy J.M. Cain System Administrator, Vex.Net http://www.Vex.Net/ IM:da...@vex.net VoIP: sip:da...@vex.net -- https://mail.python.org/mailman/listinfo/python-list
Re: [OT] Altair
Am 30.08.2016 um 17:52 schrieb D'Arcy J.M. Cain: On Tue, 30 Aug 2016 15:56:07 +0200 Joe wrote: Am 30.08.2016 um 13:01 schrieb D'Arcy J.M. Cain: On Mon, 29 Aug 2016 21:21:05 -0700 Larry Hudson via Python-list wrote: I remember it well. It's what I used to initially learn C. I'm a completely self-taught, hobby programmer. Been around since the MITS Altair. How many remember that beast?? Remember it and still have it in the basement. I read a lot about the Altair in Byte in those days, but never had a chance to touch it. Wasn't it horrible expensive? I can't remember what is was going for but I bought mine used for $1,000. It had a number of add-ons including a keyboard and floppy drives. The power supply was also beefed up. It also had a replacement bezel. It seems that the original Altair's silk screened front panel was crappy and rubbed off easily. Some company sold one but it says "Cycloid" instead of "Altair" on it. I think the first BASIC Interpreter ever sold by Gates & Friend was for this machine? How did you use your floppy drives on this machine (Open-Write-Close)? -- https://mail.python.org/mailman/listinfo/python-list
Re: [OT] Altair
On Tue, 30 Aug 2016 20:51:54 +0200 Joe wrote: > I think the first BASIC Interpreter ever sold by Gates & Friend was > for this machine? How did you use your floppy drives on this machine > (Open-Write-Close)? The floppy drive came with an operating system called MDOS - Micropolis Disk Operating System. Once you loaded it by selecting the ROM address on the front panel, setting the PC and hitting RUN it took over. There was a bit of configuration, handled through the switches, that had to be done and then any further changes were done to the image in memory and saved to disk. When I finally upgraded to a whopping 64K of RAM (with a Morrow S-100 memory board) I had to blank out the section where the disk controller sat in memory. -- D'Arcy J.M. Cain System Administrator, Vex.Net http://www.Vex.Net/ IM:da...@vex.net VoIP: sip:da...@vex.net -- https://mail.python.org/mailman/listinfo/python-list
Re: Multimeter USB output
On 08/30/2016 04:01 AM, D'Arcy J.M. Cain wrote: On Mon, 29 Aug 2016 21:21:05 -0700 Larry Hudson via Python-list wrote: I remember it well. It's what I used to initially learn C. I'm a completely self-taught, hobby programmer. Been around since the MITS Altair. How many remember that beast?? Remember it and still have it in the basement. Mine is stuffed into the back of a closet. :-) It was still working when I stored it, but I don't think I could remember how to bring it up again. As I recall, you had to set the starting memory address via the front-panel switches — but the details have long since evaporated from my memory. :-( -- -=- Larry -=- -- https://mail.python.org/mailman/listinfo/python-list
Re: Multimeter USB output
On 29/08/2016 09:54, Joe wrote: Am 28.08.2016 um 17:22 schrieb Dennis Lee Bieber: If you can read spaghetti coded C, you might want to study https://sourceforge.net/projects/ut61/ Interesting, but... The last time I did something with c, it was with BDS-C under CM/M. Somebody remenbering this no-fp compiler from the dark age before PC und Linux? Yes. It was a long time ago when I used BDS-C on initially Apple II + Microsoft CP/M card. Then on other Z80 CP/M systems. I also was introduced to the editor MINCE (Mince is not complete Emacs) which was compiled with BDS-C. 33 years ago and it seems like yesterday! -- https://mail.python.org/mailman/listinfo/python-list
Re: [OT] Altair
On 08/30/2016 11:51 AM, Joe wrote:
Am 30.08.2016 um 17:52 schrieb D'Arcy J.M. Cain:
On Tue, 30 Aug 2016 15:56:07 +0200
Joe wrote:
Am 30.08.2016 um 13:01 schrieb D'Arcy J.M. Cain:
On Mon, 29 Aug 2016 21:21:05 -0700
Larry Hudson via Python-list wrote:
I remember it well. It's what I used to initially learn C. I'm a
completely self-taught, hobby programmer. Been around since the
MITS Altair. How many remember that beast??
Remember it and still have it in the basement.
I read a lot about the Altair in Byte in those days, but never had a
chance to touch it. Wasn't it horrible expensive?
I don't think so. The figure I have in my (very fallible) mind is $300 (or maybe $600) for my
original Altair with 1K RAM and no peripherals.
I can't remember what is was going for but I bought mine used for
$1,000. It had a number of add-ons including a keyboard and floppy
drives. The power supply was also beefed up.
It also had a replacement bezel. It seems that the original Altair's
silk screened front panel was crappy and rubbed off easily. Some
company sold one but it says "Cycloid" instead of "Altair" on it.
I think the first BASIC Interpreter ever sold by Gates & Friend was for this
machine? How did
you use your floppy drives on this machine (Open-Write-Close)?
('Friend' is Paul Allan.)
My first floppy was from Northstar Computers. It used the first 5¼ drive made (by Shugart). It
came with it's own DOS and BASIC -- somewhat incompatible with Gates' Altair BASIC, but very
usable. (Anyway, Altair BASIC did not handle disks — at least the original version did not.)
The Northstar DOS was somewhat weird due to where it was located in memory. The bottom 8K of
RAM was free, the next 2K was the DOS (that's right a complete Disk-Operating-System in 2K of
memory!). The rest of available memory above that was also free. The BASIC was also loaded in
this memory above the DOS.
Trivia: (and perhaps wrong) — The original name of Northstar Computers was Kentucky Fried
Computers.
--
-=- Larry -=-
--
https://mail.python.org/mailman/listinfo/python-list
Re: What's the best way to minimize the need of run time checks?
On Wed, Aug 31, 2016 at 4:30 AM, Quivis wrote: > On Mon, 29 Aug 2016 13:09:28 +1000, Chris Angelico wrote: > >> What's the best way to minimize the need of run time checks? > > Don't do programming! > > Did I win something? You might have won the 100m dash, except that we couldn't verify your velocity of locomotion without a... run time check. Badumtish. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: [OT] Altair
> On Aug 30, 2016, at 11:51 AM, Joe wrote: > >> Am 30.08.2016 um 17:52 schrieb D'Arcy J.M. Cain: >> On Tue, 30 Aug 2016 15:56:07 +0200 >> Joe wrote: >>> Am 30.08.2016 um 13:01 schrieb D'Arcy J.M. Cain: On Mon, 29 Aug 2016 21:21:05 -0700 Larry Hudson via Python-list wrote: > I remember it well. It's what I used to initially learn C. I'm a > completely self-taught, hobby programmer. Been around since the > MITS Altair. How many remember that beast?? Remember it and still have it in the basement. >>> I read a lot about the Altair in Byte in those days, but never had a >>> chance to touch it. Wasn't it horrible expensive? >> >> I can't remember what is was going for but I bought mine used for >> $1,000. It had a number of add-ons including a keyboard and floppy >> drives. The power supply was also beefed up. >> >> It also had a replacement bezel. It seems that the original Altair's >> silk screened front panel was crappy and rubbed off easily. Some >> company sold one but it says "Cycloid" instead of "Altair" on it. > > I think the first BASIC Interpreter ever sold by Gates & Friend was for this > machine? How did you use your floppy drives on this machine > (Open-Write-Close)? Paper tape reader. The first time I came across a paper tape reader when I visited the university as a teenager in 1984. A CNC machine read the paper tape to drill six holes in a piece of metal. Chris R. -- https://mail.python.org/mailman/listinfo/python-list
Re: [OT] Altair
I had a Spectra Video, and I do remember fondly for allowing to experiment with fractal and all sorts of programming in BASIC. I recently watched the Steve Jobs movie and it was nice seeing how Apple was promoting that stage of early personal computers. On Tue, Aug 30, 2016 at 6:52 PM, D'Arcy J.M. Cain wrote: > On Tue, 30 Aug 2016 15:56:07 +0200 > Joe wrote: > > Am 30.08.2016 um 13:01 schrieb D'Arcy J.M. Cain: > > > On Mon, 29 Aug 2016 21:21:05 -0700 > > > Larry Hudson via Python-list wrote: > > >> I remember it well. It's what I used to initially learn C. I'm a > > >> completely self-taught, hobby programmer. Been around since the > > >> MITS Altair. How many remember that beast?? > > > > > > Remember it and still have it in the basement. > > > > > I read a lot about the Altair in Byte in those days, but never had a > > chance to touch it. Wasn't it horrible expensive? > > I can't remember what is was going for but I bought mine used for > $1,000. It had a number of add-ons including a keyboard and floppy > drives. The power supply was also beefed up. > > It also had a replacement bezel. It seems that the original Altair's > silk screened front panel was crappy and rubbed off easily. Some > company sold one but it says "Cycloid" instead of "Altair" on it. > > -- > D'Arcy J.M. Cain > System Administrator, Vex.Net > http://www.Vex.Net/ IM:da...@vex.net > VoIP: sip:da...@vex.net > -- > https://mail.python.org/mailman/listinfo/python-list > -- Sivan Greenberg Co founder & CTO Vitakka Consulting -- https://mail.python.org/mailman/listinfo/python-list
Re: [OT] Altair
On 2016-08-30, Christopher Reimer wrote: > Paper tape reader. The first time I came across a paper tape reader > when I visited the university as a teenager in 1984. A CNC machine > read the paper tape to drill six holes in a piece of metal. The file containing the list of coordinates generated by a CAD program for holes in a circuit board is still often referred to as a "drill tape". -- Grant Edwards grant.b.edwardsYow! Now that I have my at "APPLE", I comprehend COST gmail.comACCOUNTING!! -- https://mail.python.org/mailman/listinfo/python-list
Re: Multimeter USB output
On 08/29/2016 09:24 PM, Paul Rubin wrote: Larry Hudson writes: with BDS-C under CP/M. Somebody remenbering this no-fp compiler from the dark age before PC und Linux? I remember it well. It's what I used to initially learn C. Source code is online here: http://www.bdsoft.com/resources/bdsc.html [...] I remember reading a magazine interview with Leor Zolman (the author of BDS-C) where he mentioned what the BDS stood for... He said is was his nickname in college: Brain Dead. Actually "Brain Dead Software" it was not! It was really quite good, and rather widely used at the time. -- -=- Larry -=- -- https://mail.python.org/mailman/listinfo/python-list
Re: Multimeter USB output
Larry Hudson writes: > Actually "Brain Dead Software" it was not! Brain Damage Software, apparently: https://en.wikipedia.org/wiki/BDS_C -- https://mail.python.org/mailman/listinfo/python-list
