[erlang-questions] Issues with stdin on ports

Heinz Nikolaus Gies heinz@REDACTED
Tue Jul 30 12:01:36 CEST 2013

I am facing the same issue as Anthony,
it is rather annoying there are more issues that are involved with Erlangs handling of the STD* pipes, i.e. missing a way to terminate a program that does not terminate on STDin close. I would not argue 'because it's not in Erlang it is not important'. I greatly enjoy that Erlang is not jumping any change to change but that argument means nothing would ever get get done :P

On Jul 30, 2013, at 10:43, Jesper Louis Andersen <jesper.louis.andersen@REDACTED> wrote:

> On Tue, Jul 30, 2013 at 8:30 AM, Anthony Grimes <i@REDACTED> wrote:
> Sure, that's an option. I'm still unclear why I can do this in every other language I use but not Erlang. I find it hard to believe that all other languages with this capability are doing something utterly stupid, but Erlang, being the best language in the known universe, has gotten it utterly correct. But once again, I'll concede.
> One thing to muse about is how useful an unimplemented feature is, if said language is more than 20 years old :)
> Yes, you could add it, and it may make sense to add, but I find it way easier to hack pygments to be able to read data in {packet, 4} format.
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130730/2e661794/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130730/2e661794/attachment.bin>

More information about the erlang-questions mailing list