Re: (OT) code prototyping

[ww]

in reply to (OT) code prototyping

Can you help me understand?

If your "problem doesn't make sense in perl" why ask here?

OTOH, if you want to write code (ignoring -- for the moment -- the word "prototype" whose meaning in this context is unclear) to obtain the info you enumerated using Perl, that's not terribly complicated, nor a project which requires you to re-invent the wheel.

But, if you mean Perl is ill-suited for your ultimate project -- working code to "do something" -- and that "prototype" means something like 'automate the collection of config info' as an integral part of the ultimate project, perhaps you should pick and language you feel is well-suited, and pursue answers from those who know that language.

And if I'm being dense; well, I'm sorry about that, but please spell out just what help you hope the [Perl]Monks will provide.

[doubledecker]

Infact, I'm doing my work only in Perl and I thought prototyping code should be a fluent english. taking granted that i work in perl, how a sample prototype code looks like? I'm very much confused here....

[BrowserUk]

I thought prototyping code should be a fluent english ...

Why? The monks that come here natively speak any of dozens of different languages. Why choose fluent English instead of fluent Mandarin Chinese or fluent Urdu or fluent Serbo-Croate?

While some, maybe even most, may have a smattering of English, the one common language they all have -- assuming they're not total beginners -- is Perl.

And Perl is exactly designed for capturing the semantic necessities and nuances of computer programming. Why would prototyping in English (or any spoken language) be more appropriate?

[eyepopslikeamosquito]

I'm very much confused here....

Let me try to explain why your node was not well-received.
• Your node title "code prototyping" was too general to convey what your node was about. I clicked on your node, hoping it to be about Software prototyping, perhaps asking an interesting process question about how best to use prototyping to debug software requirements. But it wasn't. So I was disappointed. In future, spend a bit more time to find a more specific, descriptive title, for example, "How to find system information (OS version, memory, cpu, disk, ...) on Linux".
• Show some effort. Do some searching before you post. Provide any useful links you found. Show what you have tried so far, what worked well, what didn't. That way, you don't look like someone who is too lazy to do his own work and expects others to do it for him. Moreover, if you provide interesting links and ways to get Linux system information, others can learn from your efforts.
See How (Not) To Ask A Question