Re: [address@hidden: Re: Type-in programs using BASH]

[Ryan Cunningham]

I would also like the discussion on the GCC mailing list to end. The discussion 
on /source/ code, however, should remain alive and well.

Sorry for all the confusion.

And by "type-in programs", I don't mean example programs like "Hello world" 
programs. I mean real programs with real purpose.

Programs written by freelance authors that program for a living, to (hopefully) 
find a user base among even the newest of GNU/Linux users.

One day we'll be able to type in programs like these that are encoded in 
machine code. But that day is not now. For portability reasons, I'd prefer 
source code for print publication.

But, in case we ever reach that day, I won't modify my proposed GPL addendum on 
this topic.

This discussion is on a Bash mailing list, but for the same reason as above, it 
could be possible that a type-in program is published in a source code 
language, like C, that /compiles/ into machine language. In that case, it would 
have to be typed into a text editor instead of a here-document (unless your 
compiler supports reading input from here-documents).

As I pointed out to Mr. Stallman, I'd like to encourage everyone who reads 
these messages to spread the word about the idea.

-- 
Sent from my iPod

> On Jan 26, 2015, at 3:50 PM, Ryan Cunningham <rvskmbrly3@gmail.com> wrote:
> 
> No, no, not on the Internet---I mean in a paper magazine, which Internet 
> users can also get.
> 
> I'd like the machine code discussion to end.
> 
> -- 
> Sent from my iPod
> 
> On Jan 26, 2015, at 3:03 PM, Eduardo A. Bustamante López <dualbus@gmail.com> 
> wrote:
> 
>>> I am proposing this as a possible alternative or complement to publication
>>> on the Internet to take into account those without Internet access, though
>>> those *with* Internet access also get the benefit.
>> So you want to publish stuff on the Internet for people that don't have 
>> access
>> to the Internet? Right.
>> 
>> This all sounds like a waste of time. Don't type machine code. Also, in the
>> remote case that people will type machine code into their terminal, what does
>> heredocs have to do with that? Bash doesn't understand machine code.