I Plan to Invent New Software

[Ostronomos]

I just received the new C++ Primer c 2013 and it seems to be presented in a logical and understandable format which allows a new beginner who is unfamiliar with computer languages to learn it from scratch. Unlike previous editions the C++ Primer presents the advanced language of C++ rather than starting from the low level language of C. Those who are familiar with the recent history of C++ will know that the C++ standards committee issued a major revision of the C++ standard in 2011 which made the new features of the advanced language more efficient and easy to use. One of the three parts that comprise the new language, the standard library, uses the advanced language to provide useful data structures and algorithms. It also makes the standard library more efficient to use. With the knowledge that I gain from the book I am hoping to invent revolutionary new software when I boost my intelligence to supreme genius levels.

[C C]

"Great inventors have pioneering ideas, lesser minds steal them, China implements them." --Jing-sheng Guǎngchǎng

[confused2]

Personally I hate objects (as in Object Orientated Programming). The opacity of objects makes them very difficult to debug. I wrote a data logger in Python about a year ago and it crashes every two days or so. It's easier to restart it every two days than work out why it crashes. I found C inherently nasty with wandering pointers and (from memory) a tendency in the direction of memory leaks. It isn't intended to be easy to learn - if you follow the primer step by step it might be ok.

[Ostronomos]

My incredible insights in the meditative state are no doubt unparalleled by anyone in History as some of you may have gleaned from my "reality" threads.

On a Windows system, after writing a program we must compile it. The compiler generates an executable file whose name corresponds to the source file such as prog1.cc. The suffix ".cc" tells the system that it is a C++ program and the entire program and compilating is run on a console window or command prompt on Windows. "$" is the system prompt and "CC" names the compiler. So that the command that we run to compile the program looks like "$ CC prog1.cc".

A dot "." followed by a backslash places the file in the current directory and not any other. So to recap, first we write the program (which contains one or more functions one of which is "main"), then we store it in an executable file by compiling it which we do in the command-line interface in the console window.

[Syne]

Sounds like a child giving a book report on his homework assignment.

[stryder]

Personally I hate objects (as in Object Orientated Programming). The opacity of objects makes them very difficult to debug. I wrote a data logger in Python about a year ago and it crashes every two days or so. It's easier to restart it every two days than work out why it crashes. I found C inherently nasty with wandering pointers and (from memory) a tendency in the direction of memory leaks. It isn't intended to be easy to learn - if you follow the primer step by step it might be ok.

I wish you hadn't mentioned you have a datalogger with a crash problem.... those sort of things would make me sit there for hours trying to solve the puzzle. I couldn't guess without further information, however I know if the wrong datatypes are sent that it could cause problems when parsed. So if something is suppose to be strictly and integer and then it's being sent data that isn't, it could well be what throws the problem. To be honest though I would more likely access a SQL DB than just write to a file for logging, as long as it's not an overly active log system.

[confused2]

I wish you hadn't mentioned you have a datalogger with a crash problem.... those sort of things would make me sit there for hours trying to solve the puzzle.  I couldn't guess without further information, however I know if the wrong datatypes are sent that it could cause problems when parsed.  So if something is suppose to be strictly and integer and then it's being sent data that isn't, it could well be what throws the problem.  To be honest though I would more likely access a SQL DB than just write to a file for logging, as long as it's not an overly active log system.

It is an SQL DB using the Python library. There's also I2C from the sensor and interrupts (in Python) to log the data and a Flask webserver - there could be memory leaks in any or all of them. All it does is log the temperature rise from the available solar input so not mission critical which is the only reason I haven't burrowed through all of the software looking for the problem - I would've, oh yes I certainly would've - but I'm taming my OCD as I get older.
As an off topic off topic point I'm trying to get hot air (to heat the house) from a 'heat panel'. Blowing air over a hot surface doesn't pick up much heat. I'm sucking (or blowing) air through a black cotton sheet which seems to work quite well - if you (or anyone) is interested - new thread?

[stryder]

I wish you hadn't mentioned you have a datalogger with a crash problem.... those sort of things would make me sit there for hours trying to solve the puzzle.  I couldn't guess without further information, however I know if the wrong datatypes are sent that it could cause problems when parsed.  So if something is suppose to be strictly and integer and then it's being sent data that isn't, it could well be what throws the problem.  To be honest though I would more likely access a SQL DB than just write to a file for logging, as long as it's not an overly active log system.

It is an SQL DB using the Python library. There's also I2C from the sensor and interrupts (in Python) to log the data and a Flask webserver - there could be memory leaks in any or all of them. All it does is log the temperature rise from the available solar input so not mission critical which is the only reason I haven't burrowed through all of the software looking for the problem - I would've, oh yes I certainly would've - but I'm taming my OCD as I get older.
As an off topic off topic point I'm trying to get hot air (to heat the house) from a 'heat panel'. Blowing air over a hot surface doesn't pick up much heat. I'm sucking (or blowing) air through a black cotton sheet which seems to work quite well - if you (or anyone) is interested - new thread?

A quick lookup for the I²C would make me wonder if the limitation of being half-duplex would be a contributing factor.

As for recapturing heat, that's always an interesting subject (especially if a lifehack). I often wondered why heatpipes weren't placed behind solar panels to capture absorbed infrared energy rather than just capturing photo-voltaic energy.

Considering the element of a fan heater tends to be coiled many times over to generate a high enough surface area for the heat to the be pulled by airflow, it's just about solving that surface area problem.