in reply to Re: Re: perlcc?
in thread perlcc?

Thank you Juerd, for that increadibly non-instructive response.

Thank you for that increadibly non-descriptive question [the root node of this thread]. By mentioning three methods of finding answers real quick, I think I did quite well.

I'll try and make it clearer: perlcc waves_praat.pl -o waves_praat does not work.

Please compare "have been trying to find out how to use" to "found out that it does not work". And still you did not provide enough information for us to have ANY clue about what goes wrong. What are the error messages? Do you even have a compiler installed?

I would not expect to be unable to cope

The code generated in this way is not guaranteed to work. should have given you some sort of hint. You should not expect perlcc to work properly. This citation is from the manual I refered to three times, by the way.

So, my question remains: is there a module that I must use in order for perlcc to function properly

There is not. It would have been mentioned in the documentation, as Fletch already pointed out. 

- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.

Replies are listed 'Best First'.
Re: x 3 perlcc?
by dargosch (Scribe) on Apr 19, 2002 at 21:54 UTC

    Dear fellow monks,


    In this discussion (which I think has become somewhat larger than my original question to the forum entitled " Seekers of Perl Wisdom"), there is at least two separate issues:

    1) I asked why perlcc does not work. This is no longer an important question, since I found the problem (something to do with a B or O package not being compiled correctly). As Juerd and Fletch pointed out, my original posts were not very imformative, and that was of course entierly my fault, since I was conviced that this was the same problem I had last time. "Assumption is the mother of all fuckups", right?

    2) I am not sure why my original post was so offensive to Juerd that he descided to throw a RTFM on me (what is the point of this forum then, I ask). Furhtermore, I fail to see how my ability to read or write languages have any bearing on the discussion. I was under the impresion that Unicode was supposed to bring writing systems together, and that would open for some questions about perl from people that speaks very little english. I'm not sure that patronising them for it would increase the popularity of perl.

    This is, of course, just my oppinion. I'm sure there are many others.
[reply]
      2) I am not sure why my original post was so offensive to Juerd that he descided to throw a RTFM on me (what is the point of this forum then, I ask).
      I wonder how you gathered all that from a few lines of clean text (none was in bold or CAPS or funny colors and none outright called you any names or such).

      To me, an RTFM response is the first and only one. How to RTFM is an excellent guide on How to do it. When asking questions, you'll have to watch out for "it's broken" or "it doesn't work" without providing further information. Providing the error message you are getting is the first step and the least you could do. You could've also provided the code which is causing perlcc to fail, or at least enough of it to cause the problem. Also, telling us all the options you've exausted prevents, well, advice you know is not gonna work.

      Also, more good information at Before You Post ... and What makes a bad question?

      Furhtermore, I fail to see how my abi...
      *full*stop*

      Let's just stick to shop talk (ie perl). If we nip this in the bud right now, we'll all live happier. Don't read more into text than what it actually says.

      update: on a sidenote, meaningful node titles make reuse easier ~ that is, if you named your node something like "perlcc error : error text here?" anybody looking at the same error might find help here (I say might, cause, well, you know ;)

       
      ______crazyinsomniac_____________________________
      Of all the things I've lost, I miss my mind the most.
      perl -e "$q=$_;map({chr unpack qq;H*;,$_}split(q;;,q*H*));print;$q/$q;"

[reply]

In Section Seekers of Perl Wisdom