Topic awaiting preservation: Mashed windows -> Command line php rocks (Page 1 of 1)

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

please.
leave php where it belongs, creating web pages.
It is not a general purpose scripting language, even if the guys from zend claim otherwise.

Now, it might be cool to use it together with the annoying 'html-folders' windows has since 98 or so.
But that's about it.

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

http://bugs.php.net/bug.php?id=8130

I'm sure you of all people can imagine what their parser has to look like for them not being able to fix this?

And you've named most of the alternatives yourself.
Perl. Shell scripts. I'd add Python to the list, since it's got even better libraries than php (although of course the documentation isn't as good as the php manual).

PHP is great for creating web pages, especially with the 'inline html' concept.
But you're not gonna need that any where else. Or do you know an example where this would be handy?

It's fast because it calls C code for all it's library calls, which typically make up 98% of any given php script.
But have you ever tried to write your own c library for php? Recompiling is the name of the game, usually.
(Note: PHP can load libraries that are not compiled into the binary with dl(). But it seems to be a bit shaky, juding from the user's comments on the manual page).

I'm not 100% sure about it's garbage collection, but I believe it's only done when a script terminates. That'd be deadly in anything but webpages and shell scripts.
(Can't seem to quickly find information on php's gc in the usenet groups right now).

Anyhow, since all php, perl and python do is call c's malloc() for allocating memory, I wouldn't expect much speed difference (there might be some, created by different allocation strategies).

I agree that it's a big step up from 'dos .bat scripting'... after all it is turing complete.

I could spent half an hour posting shortcomings of the language itself (and not it's particular implementation), but it's hardly worth it.
(But just think about scoping in php for a moment...)

Use the best tool for the job.
PHP in my opinion is not the best tool for batch processing.

so long,
TP

ps: next time simply ask for my arguments before calling my opinions ridiculous. Thank you.

Just to defend WarMage -- if you're thinking about my thread about Java streaming, what Mage said was "Current networking technologies make it pretty difficult to do this, I am sure it can be done, I am not sure of the quality." He was talking about internet bandwidth, not Java itself.

That said, I always learn a good deal from these discussions of the less well-known sides of different languages. Just keep it polite, guys.

Cell 1250 :: alanmacdougall.com :: Illustrator tips

Well, I am not sure where my name came up in this thread, but thanks for the defense none the less. I was talking about bandwidth to some extent, but more to an extent I was talking about the TCP/IP stack implementation, which isn't perfect for streaming video (small packet size, packet retransmissions etc.).

As for the idea of php on the command line, I don't see a problem with it. I would actually like to see more uses for this. Give me a reason to dump perl. Perl is a great language, but I would rather not waste my time with it as it is so very unstructured, even when you use strict; PHP has a bit more concrete structure to it, and as a function based language seems just right for batch scripting and directory surfing.

I don't know why you would need to argue the validity of using one language over another. I though we (as the programming community) put this issue to rest, by saying "use what you know, use whatever tool gets the job done." If you can make it work then there is no reason you shouldn't use what you are using. Some people choose to use a regular hammer, some use industrial strength air powered hammers, and some people use that new fangled hammer that looks kind of weird. They all drive the nail home, so there is little reason to ague about which tool you use, as a skilled craftsman will be just as fast using any of the above mentioned and just as competent using any of the above mentioned.

From that, how about you post some examples, because I for the life of me can't figure out exactly what you are doing.


Me

Mr. Mage:

quote:

---

It's a bit like Warmage claiming Java is not the good tool for streaming medias

---

There you go...