[ruby-talk:00571] Re: New feature request! :-)

Hi,

In message "[ruby-talk:00570] Re: New feature request! :-)"
    on 99/08/06, [e-mail] <[e-mail]> writes:

|Now I would like to ask you, whether the Ruby license allow us to use
|Ruby for that purpose? Our company wouldn't allow to publish the
|sources!!! :-(

Sure.  You don't have to publish your source.

See README for the license.  In summary, you can do whatever you want
with Ruby, except:

  * distribute modified Ruby pretending my distribution.
  * distribute binary without pointing where to get source.

So, you can copy, modify, distribute, and even sell Ruby.  In
addition, there's no restriction about code written in Ruby.

|But Ruby already do a good job to detect, whether a statement is really
|finished or not. :-)

I tried my best.

|But here, IMHO, Ruby would not need the `\'! Because if Ruby find two
|string literals following each other with *ONLY* whitespaces
|in-between, it could simply concatenate them; or is there something I
|miss here?
|
|A string statement (means a line with only a string) makes no sense, or?

Sometimes it makes sense, for example:

  def foo
    print "this is in foo\n"
    "foo"
  end

the method `foo' should print "this is in foo\n", then return the
string value "foo".

|>   * String concatenation is not that heavy unless it appears in inner
|>     most loop.
|
|Ohh! It is ;-) If the parser could do it, it would costs 0 us during
|runtime. If you have to do it yourself, it costs xxx us. That is much
|more, isn't it? ;-))))
|
|On every case, it is a penalty!

I agree.  If I can find good way to do compile time string
concatenation, I'd like to add it, maybe in Ruby 1.5.

                                                        matz.