Posted by asotobu on Jun 01, 2013; 11:58pm
URL: https://discuss.asciidoctor.org/Asciidoctor-0-1-3-attributes-and-conflict-with-AJI-tp258p263.html

Well in fact RubyHash implements Map so no problem in that way but because Option class is a model class which could be used when we integrate AJI with Javascript (if we find useful of course) I would like to maintain Option class free of JRuby dependencies

El diumenge 2 de juny de 2013, lightguard.jp [via Asciidoctor :: Discussion] ha escrit:

Another possibility is to create our own implementation of a map that also implements the RubyHash interface as well, no reason we couldn't do that. 

—
Sent from Mailbox for iPhone

On Sat, Jun 1, 2013 at 4:30 PM, asotobu [via Asciidoctor :: Discussion] <[hidden email]> wrote:

well it is clean, the problem is that you iterate through a Map for moving all elements from one kind of map to another kind of map, so it is a problem of performance more than something that it cannot be understood. Also I must admit that when I have seen all my tests failing I have entered on panic time and for this reason I have written a post on this forum, but the solution of the problem is easy to understand.

Tomorrow I will release the 0.1.3 version, so Maven, Gradle, Asciidoclet, Viewers, ... can upgrade.

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Asciidoctor-0-1-3-attributes-and-conflict-with-AJI-tp258p261.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Asciidoctor-0-1-3-attributes-and-conflict-with-AJI-tp258p262.html

To unsubscribe from Asciidoctor 0.1.3 attributes and conflict with AJI, click here.
NAML

--
Enviat amb Gmail Mobile