Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number

Please post your code! (was: Re^3: Win32::Console question.)

by roboticus (Chancellor)
on Dec 17, 2007 at 19:19 UTC ( #657488=note: print w/replies, xml ) Need Help??

in reply to Re^2: Win32::Console question.
in thread Win32::Console question.


You might be embarrassed to have anyone see your code, but it's still a good idea to post code. Don't worry, no-one's here to pick on someone just because they're starting out or otherwise lacking knowledge.

  • Many problems aren't where the questioner thinks, so relevant information is left out. This will cost you and the people helping you of valuable time.
  • Some problems are easily recognized by inspection. No code ... no inspection! You're depriving someone of the chance to give you an immediately useful answer. Otherwise, it may take several exchanges to get the relevant information.
  • Many people will skip nodes without code, as they don't want to create an example from scratch. Many times it's much easier to fix something that's already there. Additionally, many monks are interested in helping those who make an effort. If the problem's not important enough for you to give a good, clear problem statement, then why is it worth my time? There's no shortage of questions to choose from. A chunk of code goes a long way in this regard (think "sweat equity").
  • Seeing your code gives a monk a general idea as to your skill level. That helps them not give advice at too high or too low a level. It also gives them the opportunity to offer advice on a particular concept that you're not clear on, or show you an interesting coding technique that could save you time.
  • Comment on Please post your code! (was: Re^3: Win32::Console question.)

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://657488]
[LanX]: before digging into deep debugging ... I have a strange UTF8 problem, probably it rings a bell:
[LanX]: two utf8 strings from different sources are base64 encoded, but after joining both the umlauts in teh second get deleted
[Corion]: LanX: You can't just join two base64 strings together
[LanX]: (not a high priority bug because I can use some HTML entities in the second string)
[Corion]: base64 is padded to a multiple of 4 chars (or something)
[LanX]: misunderstanding, I joined them before converting to base64
[Corion]: Also, I would be wary of encodings and try to make really sure that both input strings are UTF-8. Maybe join the input strings from one source together to see whether they decode as bad or not

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (9)
As of 2017-01-16 13:51 GMT
Find Nodes?
    Voting Booth?
    Do you watch meteor showers?

    Results (150 votes). Check out past polls.