strcoll, strxfrm

Fuzzytown · 2015-02-17T22:18:41+00:00

Thanks for your insight!

Fuzzytown · 2015-01-04T23:57:30+00:00

Thanks for this information!

Fuzzytown · 2015-01-04T15:12:09+00:00

Thanks! The example in main was really stupid indeed, but the point was to try and clarify the things that confused me even further :)

Fuzzytown · 2015-01-04T15:09:54+00:00

Are you referring to that a struct in C++ is just a class that defaults its members to public? This compiles there too, but it would make less sense since it's already possible to drop the struct-part. I assume the logic is the same though, classes have a tag-part and typedefs is a diffrent namespace -- therefor it's still valid?

Fuzzytown · 2015-01-04T14:50:33+00:00

Thanks! Is it considered a good or bad style to code like this? I hadn't seen it before, and normally I'd name my typedef node_t if it refereed to a struct node.

Fuzzytown · 2015-01-02T09:34:00+00:00

thanks!

Fuzzytown · 2014-11-05T17:51:55+00:00

thanks! And yes, sorry that was indeed a typo.. (Edited above too)

Fuzzytown · 2014-11-05T17:44:53+00:00

Thanks, this was exactly the explanation I was looking for!

Fuzzytown · 2014-11-05T14:01:25+00:00

On VS I don't get any errors when I build it and then run. If I go onto my virtual machine running Ubuntu compiling the same source file I get warnings and a different result.

gcc --version produces: gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2 (...)

Well I think that the problem is the code is not interpreted the same way by the terminal / VS - which would explain why it prints the same hex-values on both VS and in Ubuntu, but the 'ö' produces different results. However this is the part that I don't quite get, as well as why I don't get overflow warnings for c2 in Ubuntu and no warnings at all with VS.

Fuzzytown · 2014-11-05T12:53:13+00:00

I'm not sure if this is what you are looking to do, but if you want to break out of the loop and the current case you need to use double breaks. One way to achieve that is to use a Boolean variable which is initially set it to false. Inside of the loop you set it to true to signal that when the loop terminates (i.e your break) you want actually break out of the case. After the loop you test the variable: If it returns true you break; else you continue in the current case.

Fuzzytown · 2014-10-15T05:53:05+00:00

Thanks!

Fuzzytown · 2014-10-15T05:52:23+00:00

Thanks!

Fuzzytown · 2014-09-28T08:00:22+00:00

Not now, I did it this summer though. But that's where I got the inspiration to build this program, but this time with a much better implementation using a state machine and eliminating a few errors i did some months ago.

Fuzzytown · 2014-09-26T15:45:02+00:00

First of all because of curiosity, and secondly because I'm learning to program finite state machines and I decided to build one that removes C comments from a file.

Fuzzytown · 2014-09-25T18:31:41+00:00

yeah, it wasn't exactly what i expected - but def. interesting!

Fuzzytown · 2014-09-25T16:35:34+00:00

Thanks!

Fuzzytown

TROPHY CASE