Learning C with the Amiga

[Louis Dias]

In that case, the USA is not a 1st world country.
Healthcare costs are quite a political debate around here.

[Louis Dias]

OT:
I am Portugues born, American raised.
I see this country with clear eyes.  It has many problems that foreigners don't see and I'm not a blind loyalist like many seem to be.

The problem with this government is that politicians also have business interests.  There should be a law separating the 2.  That is the root of many woes.  Everybody is in it for money and not for what is right.

[Louis Dias]

koaftder wrote:
c may be a pain for dealing with strings withouth a nice string lib but at least its not like vb.net on opening a file handle:

FILE * bla = fopen("c:\koft\pov.c","w");

vs

Dim bla As New System.IO.FileStream("c:\koft\POV.c", System.IO.FileAccess.Write)

(;

LOL, you make it sound like you typed every letter of that code.  The IDE's auto-complete and selection as soon as you hit the "." reduces the actually typing greatly.

Also, a simple:
imports System.IO

at the top of your code (similar to a #include) and all you'd need in the code is:

Dim bla as New StreamWriter("c:\koft\POV.c")

[Louis Dias]

Karlos wrote:

falemagn wrote:
@ Cymric

Why would a text parser need to concatenate strings?

My point exactly. All the parsing I've done, if anything usually involved breaking text up into smaller tokens, not concatenating them into larger ones.

So you've never built SQL statements on the fly based on parameters in a filtering selection screen for a program that generates a report?

[Louis Dias]

Ok, I've written code that parses a file and replaces one text/byte(s) code with another.  Now in VB6, you can read a 2MB file into a string, in memory, and doing a simple replace all at once and then writing over the old file was much faster than the traditional line by line method of drilling through the file, while writing to another followed by the delete of the old one and rename of the new to match the old.

It came in handy when converting large .CSV files with lines terminated with CR to CR/LF and vice versa.

File access is slow compared to memory access, hence having the entire file in memory was ideal and VB's "Replace" command allows you to use any sequence of bytes.  It's not just limited to 7 bit ascii.

This turned a batch processing job of many large files into one that went from taking over an hour to taking just several minutes.

[Louis Dias]

CannonFodder wrote:

Why use VB to do the job of PL/SQL(T-SQL etc)?

Anyway, isn't this thread supposed to be about learning C?  What point are you trying to achieve by spamming it with off topic crap about how superior VB is?

Start another thread and discuss it there.

Stop being ignorant, I was giving Karlos an example where string concacting becomes useful and saves time.

[Louis Dias]

koaftder wrote:
Many years back, a girl invited me to come to her place with offerings of food to teach her in the ways of programming. We both worked for a medical supply store, she did data entry, I wrote the software she slaved with. We hit it off and after a while I discovered she had tourettes and months later I was dumped via email. Karlos beware...  :-D

Are you sure it wasn't the C causing her to mouth off?  When she finally got sick of it, she sent you an email...
:ponder:
.
.
.
.
.
:devildance: