|
Yeah - temporary ones!
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
|
Check his rep graph. You will come to know about the bug.
Regards - Kunal Chowdhury | Microsoft MVP (Silverlight) | CodeProject MVP | Software Engineer
|
|
|
|
|
Check out the forum at the bottom of JavaScript For Beginners. At first, it appears to have 5 messages. However, once I expand this message, it shows 50 or so messages. Same on Chrome, FF, and IE8.
|
|
|
|
|
Thanks - all fixed.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
...for dedicated iOS, WP7, BlackBerry and Android forums? The existing catch-all Mobile forum reminds me of CP in its infancy[^]. 
Note, this is a purely selfish request. (I currently get my Android fix at StackOverflow).
/ravi
|
|
|
|
|
So what's better: a dedicated forum, or simply hanging out in Quick Answers and giving the Android [^]tag a run for it's money?
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Tags are more "efficient" but I believe a dedicated forum will have more appeal to end users. It's more efficient (imho) to visit a dedicated forum than scan a bunch of posts for relevance. That being said, I think it's fair to expect the number of posts in non-.NET forums to be low unless CP chooses to actively attract developers of other platforms. That's a decision you and DC are prolly best equipped to make.
I find StackOverflow appealing for 2 reasons: (a) less "fluff" (no VB-haters or juvenile anti-posts) and (b) platform agnostic. Lately, Google's been finding more relevant answers to programming questions on SO than CP. It didn't used to be that way.
/ravi
|
|
|
|
|
|
Fix one bug[^] create another I guess. 
3x12=36
2x12=24
1x12=12
0x12=18
|
|
|
|
|
at the bottom it says "closed because the post is not ...", I'm not sure what that means, but it probably won't become publicly visible as is.
Luc Pattyn [My Articles] Nil Volentibus Arduum
The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Please use <PRE> tags for code snippets, they improve readability. CP Vanity has been updated to V2.3
|
|
|
|
|
This tip/trick has 2 alternates that are in pending status. It seems that one alternate is a duplicate of the other (at least, it's the same idea but with slightly different code). I wanted to report one as a duplicate, but I don't see that option. I see there is a "plagiarized" option, but I don't think it is plagiarism, as I'm guessing the second poster couldn't see the first alternate while it was in pending status.
|
|
|
|
|
I don't think it makes sense to report one or the other simply because tbey are very similar solutions arrived at by different people.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
So a third person could come in, change a variable name or some formatting, and then post their alternate too? I don't think we want the same alternate posted several times. And I'm also not sure about the reporting, but it seems like that is supplanting the ability to delete alternates outright.
|
|
|
|
|
I just noticed angular brackets that aren't HTML tags behave more intuitively now inside PRE blocks, so showing a code snippet with generic lists got much easier, no more < required here:
List<SalesTeam> teamsNorth=new List<SalesTeam>();
List<SalesTeam> teamsSouth=new List<SalesTeam>();
List<SalesTeam> teamsNorth=new List<SalesTeam>();
List<SalesTeam> teamsSouth=new List<SalesTeam>();
List<SalesTeam> teamsNorth=new List<SalesTeam>();
List<SalesTeam> teamsSouth=new List<SalesTeam>();
Can you confirm this now is intended behavior and will remain for future use? Thanks.
BTW: not sure what is going on with the coloring though, the above has no lang, lang='cs' and lang='cpp' respectively.
Luc Pattyn [My Articles] Nil Volentibus Arduum
The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Please use <PRE> tags for code snippets, they improve readability. CP Vanity has been updated to V2.3
|
|
|
|
|
... and if it is intended, please fix the syntax coloring. Left and Right brackets should be treated equally.
Makes me wonder what it does with inequality statements.
bool foo = 5 < 4;
bool bar = 5 > 4;
bool baz = (5 < 4) && (5 > 4);
Edit: At least the fail is consistent.
3x12=36
2x12=24
1x12=12
0x12=18
|
|
|
|
|
The weird colouring is because of the weird (ie non-) encoding of the brackets is confusing the colouriser. I'll make a note to look into that.
Sorry - dug in deeper and it's simply because in C++ we colourise < and >, but not in C#. The reason the < gets colourised is because we HTML encode that for those who forget to, but we don't touch the > because browsers are good at handling them.
I'll change my note to make this more consistent.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
OK, sounds good.
However the main question was: is the "we accept HTML look-alikes and will handle them properly (i.e. escape them), so you don't need to escape generics any more inside PRE blocks" rule a given now?
Luc Pattyn [My Articles] Nil Volentibus Arduum
The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Please use <PRE> tags for code snippets, they improve readability. CP Vanity has been updated to V2.3
|
|
|
|
|
Just out of curiosity: Are you building a library of code fragments you are planning to post? 
|
|
|
|
|
I've got a ton of rubble under the desk if anyone wants those kind of code fragments.
Ooh - you mean non-broken, things-that-work type fragments...
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
you keep code fragments in a ton? I prefer a disk, in my experience search works better on disk-based material.
Luc Pattyn [My Articles] Nil Volentibus Arduum
The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Please use <PRE> tags for code snippets, they improve readability. CP Vanity has been updated to V2.3
|
|
|
|
|
Luc Pattyn wrote: we accept HTML look-alikes and will handle them properly (i.e. escape them), so you don't need to escape generics any more inside PRE blocks
It's more "We try and do our best to handle improperly encoded < entities". This is in the code and I've no plans to remove it.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
I can live with that; I would however prefer a more predictable behavior, maybe a simple whitelist containing the few valid HTML tags you are recognizing and letting through, assuming everything else gets escaped.
Said whitelist could then be added to the "Using PRE tags" T/T for all to read.
Luc Pattyn [My Articles] Nil Volentibus Arduum
The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Please use <PRE> tags for code snippets, they improve readability. CP Vanity has been updated to V2.3
|
|
|
|
|
Mark ==> Luc ==> Mark ==> Luc ==> Mark ==> Luc ==> Mark ==> Luc ==> Mark ==> Luc ==> ENOMEMORY
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
