comment on

maybe your post was down voted by people who had no idea what you were talking about and didn't see any indication that it had anything to do with Perl?

something as simple as [code:// ... ] around the word Starman might have tipped folks off so they had some vague clue as to what you were talking about.

You might have also alienated fewer people if, instead of saying "I've tried searching google for starman bugs", you had maybe said that you were aware of the starman issue tracker but didn't see anything there that looked similar.

Or maybe people would have been more inclined to offer advice, and not down vote, if instead of saying "I'm wondering what my code is doing wrong to cause the problem in starman" you had said "here is an example of some code that triggers this behavior in starman, can anyone see anything that might be triggering a problem like: <code>...</code>"

But these are all just guesses.

In reply to Re^2: Starman problem by hossman
in thread Starman problem by Logicus

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks