Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2010-12

Ruby-scripting for FPC and Lazarus

11 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

ik

I'ved started working on SynEdit syntaxt for
Ruby<https://github.com/ik5/SynEdit-syntaxes>but lack of time stopped me.

I have not yet looked on your work, but regardless, It's a good thing what you are doing, and I know at least myself that will love for such support, and if I'll have time for it, I will be willing to help you.

Ido

LINESIP - Opening the source for communication
http://www.linesip.com
http://www.linesip.co.il

Ivan Shikhalev wrote 20 lines
I wrote the packages for Lazarus, allowing to use Ruby 1.8 as a scripting engine in Lazarus-programs. At the moment, work is just begun, but something than it is already possible to use, as supported by published-property and obtain component through its owner by name. I would like to know whether this project will interest anyone else, and what will wish. Address of project: http://github.com/shikhalev/ppruby There is also a simple example -- in the subdirectory 'sample'. -- ---------- Ivan Shikhalev Jabber ID: _______________________________________________ fpc-pascal maillist - http://lists.freepascal.org/mailman/listinfo/fpc-pascal

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20101223/6eef2108/attachment.html>

Reply by email

Unknown author
Ivan Shikhalev wrote 11 lines
I wrote the packages for Lazarus, allowing to use Ruby 1.8 as a scripting engine in Lazarus-programs. At the moment, work is just begun, but something than it is already possible to use, as supported by published-property and obtain component through its owner by name. I would like to know whether this project will interest anyone else, and what will wish. Address of project: http://github.com/shikhalev/ppruby There is also a simple example -- in the subdirectory 'sample'.

Impressive :-)

Any particular reason why you added the version number to most of the filenames ? As soon as 1.9 (or whatever version) comes out, you'll have to change all filenames ?

I can understand you do it for the low-level files (ruby18.pp), but fail to see why you would do it for the rest ? It will make it difficult to upgrade.

Michael.

Reply by email

ik
to Unknown author
Show quoted text 24 lines
On Thu, 23 Dec 2010, Ivan Shikhalev wrote: I wrote the packages for Lazarus, allowing to use Ruby 1.8 as a > scripting engine in Lazarus-programs. > At the moment, work is just begun, but something than it is already > possible to use, as supported by published-property and obtain > component through its owner by name. > > I would like to know whether this project will interest anyone else, > and what will wish. > > Address of project: http://github.com/shikhalev/ppruby > There is also a simple example -- in the subdirectory 'sample'. > Impressive :-) Any particular reason why you added the version number to most of the filenames ? As soon as 1.9 (or whatever version) comes out, you'll have to change all filenames ?

1.9 is the development version of Ruby 2. Currently the version is 1.92 to be exact :)
Every version of Ruby, that is 1.8 vs 1.6 have different language support etc... Like that FPC 2.5.1 have additional support for stuff that 2.4 does not, and 2.2 does not have features of the language that 2.4 have.

Show quoted text 7 lines
I can understand you do it for the low-level files (ruby18.pp), but fail to see why you would do it for the rest ? It will make it difficult to upgrade. Michael.

Ido

Show quoted text 8 lines
-- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20101223/6735243d/attachment-0001.html>

Reply by email

Ivan Shikhalev
to Unknown author: Impressive :-) Any particular reason why you added the version number to most of the…

2010/12/23 :

Any particular reason why you added the version number to most of the filenames ?

I don't know how many differences would be in 1.9 version, and will it possible to make a compatible packages for all version of Ruby...

I can understand you do it for the low-level files (ruby18.pp), but fail to see why you would do it for the rest ? It will make it difficult to upgrade.

Perhaps you're right. I beg to treat the current state of the project as a highly unstable - the overall structure are just beginning to be established. In particular for this I started the discussion.

---------- ? ?? Ivan Shikhalev ? ?? Jabber ID:

Reply by email

Michael Van Canneyt
to Ivan Shikhalev
Ivan Shikhalev wrote 13 lines
2010/12/23 : > Any particular reason why you added the version number to most of the > filenames ? I don't know how many differences would be in 1.9 version, and will it possible to make a compatible packages for all version of Ruby... > I can understand you do it for the low-level files (ruby18.pp), but fail to > see why you would do it for the rest ? It will make it difficult to upgrade. Perhaps you're right. I beg to treat the current state of the project as a highly unstable - the overall structure are just beginning to be established. In particular for this I started the discussion.

I would think that only the low-level file contains the version number.

The high-level API can initially choose the API by means of a conditional define, or, at a later stage, load the low-level support 'on demand', adapting to whatever version is there.

Michael.

Reply by email

Ivan Shikhalev
to Michael Van Canneyt

2010/12/24 Michael Van Canneyt :

Show quoted text 5 lines
I would think that only the low-level file contains the version number. The high-level API can initially choose the API by means of a conditional define, or, at a later stage, load the low-level support 'on demand', adapting to whatever version is there.

Agreed. This is reasonable. Especially because I already use the dynamic loading of library. Perhaps, it's possible to do without a conditional compilation.

---------- ? ?? Ivan Shikhalev ? ?? Jabber ID:

Reply by email

Ivan Shikhalev
to Ivan Shikhalev

PS. The static linking unit is not used in "script engine". It may be user for writing Ruby extensions.

2010/12/25 Ivan Shikhalev :

Show quoted text 17 lines
2010/12/24 Michael Van Canneyt : > I would think that only the low-level file contains the version number. > > The high-level API can initially choose the API by means of a conditional > define, or, at a later stage, load the low-level support 'on demand', > adapting to whatever version is there. Agreed. This is reasonable. Especially because I already use the dynamic loading of library. Perhaps, it's possible to do without a conditional compilation. -- ---------- ? ?? Ivan Shikhalev ? ?? Jabber ID:
---------- ? ?? ???? ??????? ? ?? ICQ# 126-378-137 ? ?? Jabber ID:

Reply by email

Unknown author
to Ivan Shikhalev
Ivan Shikhalev wrote 6 lines
2010/12/24 Michael Van Canneyt : > load the low-level support 'on demand', > adapting to whatever version is there. Done. The new version is at https://github.com/shikhalev/ppruby

I get an error:

fsb: >git pull https://github.com/shikhalev/ppruby fatal: https://github.com/shikhalev/ppruby/info/refs not found: did you run git update-server-info on the server? fsb: >git pull http://github.com/shikhalev/ppruby
fatal: http://github.com/shikhalev/ppruby/info/refs not found: did you run git update-server-info on the server?

Michael.

Reply by email

Ivan Shikhalev
to Unknown author

2011/1/18 :

Show quoted text 8 lines
I get an error: fsb: >git pull https://github.com/shikhalev/ppruby fatal: https://github.com/shikhalev/ppruby/info/refs not found: did you run git update-server-info on the server? fsb: >git pull http://github.com/shikhalev/ppruby fatal: http://github.com/shikhalev/ppruby/info/refs not found: did you run git update-server-info on the server?

What's about git pull git://github.com/shikhalev/ppruby.git ?

---------- ? ?? Ivan Shikhalev ? ?? Jabber ID:

Reply by email