librelist archives

« back to archive

INTERNALS and TYPED_INTERNALS

INTERNALS and TYPED_INTERNALS

From:
Paolo Redaelli
Date:
2011-10-27 @ 09:49
Are we going to change those?
You may read in their header: "WARNING: This interface is tentative and 
may change to a large extent from SmartEiffel 2.2 to SmartEiffel 2.3."
Does it still apply? I mean are you aware of any required design change 
in them or I may assume that they are "stable" for a reasonable span of 
time (at least 6 months)?
They seems to me pretty nice and usable.
As I'm trying to re-implement deep_copy in Eiffel I may want to make it 
somehow INDEXABLE or ITERABLE feature (think do_all and for_all instead 
of iterate), perhaps adding (expanded) iterators for 
type_attribute_name, type_attribute_generator, 
type_attribute_generating_type, and object_attribute.
Why adding iterable-like feature? I too often put off-by-one bugs in my 
code.
 
 
 --
 Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP
autenticato? GRATIS solo con Email.it http://www.email.it/f
 
 Sponsor:
 Capodanno al mare in all inclusive, Euro 75 a persona, incluso cenone di 
San Silvestro, sconto bambini 50%, bimbi gratis 0-3 anni, nei Torre 
Pedrera Hotels
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=11894&d=27-10

Re: [libertyeiffel] INTERNALS and TYPED_INTERNALS

From:
Cyril Adrian
Date:
2011-10-30 @ 17:55
Hi Paolo,

2011/10/27 Paolo Redaelli <paolo.redaelli@email.it>

> Are we going to change those?
> You may read in their header: "WARNING: This interface is tentative and
> may change to a large extent from SmartEiffel 2.2 to SmartEiffel 2.3."
> Does it still apply? I mean are you aware of any required design change
> in them or I may assume that they are "stable" for a reasonable span of
> time (at least 6 months)?
> They seems to me pretty nice and usable.
>

Yes, that they are. But I'd like to extend the interface with the
possibility to call features. I don't know how, yet.


> As I'm trying to re-implement deep_copy in Eiffel I may want to make it
> somehow INDEXABLE or ITERABLE feature (think do_all and for_all instead
> of iterate), perhaps adding (expanded) iterators for
> type_attribute_name, type_attribute_generator,
> type_attribute_generating_type, and object_attribute.
> Why adding iterable-like feature? I too often put off-by-one bugs in my
> code.
>

??? I'm not sure I understand… Do you have some code snippet to share?

Cheers,

*Cyril ADRIAN*
*http://www.cadrian.net/cyril*
[image: Facebook] <https://www.facebook.com/cyril.adrian> [image:
Twitter]<https://twitter.com/cadbart> [image:
LinkedIn] <http://fr.linkedin.com/in/cadrian> [image: Google
Plus]<https://plus.google.com/100388810006463519079/posts> [image:
Google 
Calendar]<https://www.google.com/calendar/embed?src=1t93vvvrdc26ee0f83p0cunj60%40group.calendar.google.com&ctz=Europe/Paris>
Contact me: [image: Google Talk] cyril.adrian@gmail.com
 [image: Twitter] <http://twitter.com/cadbart> Latest tweet: [Liberty]
http://t.co/q6wvjgvh Cyril Adrian - using debug keys instead of always
commenting in/out the debug compounds
Follow @cadbart <http://twitter.com/cadbart> Reply

<http://twitter.com/?status=@cadbart%20&in_reply_to_status_id=129056316374261760&in_reply_to=cadbart>
Retweet

<http://twitter.com/?status=RT%20%40cadbart%3A%20%5BLiberty%5D%20http%3A%2F%2Ft.co%2Fq6wvjgvh%20Cyril%20Adrian%20-%20using%20debug%20keys%20instead%20of%20always%20commenting%20in%2Fout%20the%20debug%20compounds>
 06:46 Oct-26<http://twitter.com/cadbart/statuses/129056316374261760>
  Get this email app!

<http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps>

[image: My QR VCard]
  Get a signature like this.

<http://r1.wisestamp.com/r/landing?promo=17&dest=http%3A%2F%2Fwww.wisestamp.com%2Femail-install%3Futm_source%3Dextension%26utm_medium%3Demail%26utm_campaign%3Dpromo_17>
CLICK

HERE.<http://r1.wisestamp.com/r/landing?promo=17&dest=http%3A%2F%2Fwww.wisestamp.com%2Femail-install%3Futm_source%3Dextension%26utm_medium%3Demail%26utm_campaign%3Dpromo_17>