Friday Programming Quiz [modified]

Rama Krishna Vavilala

Right direction but can be further simplified:).

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

Alvaro Mendez

One implementation, in C#:

string DisplayNameFromColumnName(string value)
{
return Regex.Replace(Regex.Replace(value, "([a-z])([A-Z])", "$1 $2"), "([A-Z])([A-Z][a-z])", "$1 $2");
}

Regards, Alvaro

A casual stroll through the lunatic asylum shows that faith does not prove anything. - Friedrich Nietzsche

Nish Nishant

Rama Krishna Vavilala wrote:

Right direction but can be further simplified.

I forgot about the capture syntax in C# - so didn't use them :-)

Regards, Nish

Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. (*Sample chapter available online*)

Rama Krishna Vavilala

I prefer String.replace to join.

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

Rama Krishna Vavilala

Christian Graus wrote:

IUseHTMLALot

Yes! But this is a fun Quiz ignore those issues.

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

Nish Nishant

Rama Krishna Vavilala wrote:

Right direction but can be further simplified.

Simpliefied version :-

static string Func(string str)
{
return new Regex("([a-z])([A-Z])").Replace(
new Regex("([A-Z])([a-z])").Replace(str, " $1$2"), "$1 $2");
}

Regards, Nish

Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. (*Sample chapter available online*)

Rama Krishna Vavilala

What about something like "Name";)

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

Steve Echols

Seeing all these solutions reminds me I really need to learn regex. :^)

- S 50 cups of coffee and you know it's on!

Shog9 0

I wrote it that way at first, then realized it was leaving an extra space on the end, then got bored and switched to join(). I like join(). I've seen it poorly-implemented too often not to love a library implementation. ;)

PIEBALDconsult

I can put SPACEs in my column names; it's not a good idea, but I can. I suppose I can get the description from the metadata and use that if it's not empty. And I just don't think there's a 100% fool-proof way of doing the task, so why bother?

Shog9 0

Christian Graus wrote:

IUseHTMLALot

I hate those. It may be incorrect, but i'll still write it as IUseHtmlALot.

Nish Nishant

Rama Krishna Vavilala wrote:

What about something like "Name"

Blast! It adds a space to the beginning. Oh well, a call to Trim() should fix that.

Regards, Nish

Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. (*Sample chapter available online*)

Rama Krishna Vavilala

I agree that there is no 100% fool proof way esp. for cases like IUseHTMLALot or XMLValue. But this is for fun.

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

Chris Losinger

as long as you're taking out the CAPSLower case

string DisplayNameFromColumnName(const char*l)
{
string O = "";

while (\*l)
{
	O += \*l;
	O += (islower(\*l) && isupper(\*(l+1))) ? " " : "";
	l++;
}

return O;

}

image processing | batch image processing | blogging

Rama Krishna Vavilala

BTW: Probably that is why the .NET naming guidelines state that any acronym > 2 letters should not be all capitalized.

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

Matt Gerrans

Well, all we need to do is just compile his solution with the Plain English compiler and try it out! Grande?

Matt Gerrans

Shog9 0

Don't feel like firing up the compiler, but felt like being old-school...

/*
* colName points to column name, cannot be NULL
* output points to buffer suitable for holding display name, cannot be NULL
* maxOutputLen is the maximum number of characters that can be stored in output,
* excluding the inevitable NULL terminator. output must be maxOutputLen+1 chars in length
*/
char* DisplayNameFromColumnName(const char* colName, char* output, int maxOutputLen)
{
int inPos = 0;
int outPos = 0;
while ( colName[inPos] && outPos < maxOutputLen)
{
if ( isupper(colName[inPos]) && colName[inPos+1] && !isupper(colName[inPos+1]) )
{
output[outPos++] = ' ';
if ( outPos == maxOutputLen )
break;
}
output[outPos++] = colName[inPos++];
}
output[outPos] = '\0';

return output;
}

Matt Gerrans

IUseHTMLALot is problematic, but XMLValue seems okay. If you have any sequence of caps followed by lowercase, then you break before the last cap, right?

Matt Gerrans

PIEBALDconsult

I can't. If I do a thing I want to do it right (or at least handle all the known problems). How about fields "PriceAtCompUSA" and "IsOwnedByPaulMcCartney" Plus, breaking the field names will make it difficult to parse the resultant file. It's just not worth the effort. Well, unless I'm getting paid.

Shog9 0

Eh, it's just another hammer. And the truth of it is, code with too many regexps in it can be nearly unmaintainable. Great for code that won't last long or that should be replaced rather than tweaked... not so good for code intended to grow and mature.