[erlang-questions] A few type-related 18.0 questions

Olivier BOUDEVILLE olivier.boudeville@REDACTED
Fri Jul 17 18:01:52 CEST 2015


Hello Tuncer,

[...]

> Are you saying that
> 
> (1) because the module doesn't exist as a .beam file Dialyzer doesn't
> know of its existence

In this particular case, the generated module exists neither as a source 
file (.erl) nor as a compiled one (.beam), as it exists only at runtime 
and in-memory - so I do not think Dialyzer has any chance to be aware of 
it and of its actual content (exports)?

> 
> (2) and there's no way to make the ephemeral/volatile module known to
> Dialyzer as part of the analysis call
> ?

Ah, maybe there is such a solution that I am not aware of, but apart from 
running a Dialyzer attached to the application (a bit like an attached 
gdb), I do not think Dialyzer can do much there. So I was looking for a 
way to silence it whenever it saw calls from anywhere in the code to any 
function defined in these pseudo-modules.

To clarify the use case, this pseudo-module generation serves to create 
efficient look-up tables of immutable data that is known only at runtime 
(ex: after having read a data file).

Have a nice week-end!

Best,

Olivier.


> > In this case I do not think we can tell Dialyzer to suppress this
> > warning (since the -dialyzer attribute seems to be meant to be used
> > in the sources *of the module itself*, i.e. it would have here to be
> > specified in the sourceless M2).
> >
> > This is not a big issue (and these are edges cases indeed), but it
> > would be interesting if we could define 'global' suppressions, or
> > that would apply to a set of modules (similarly, Dialyzer would not
> > be able to see that conditional calls could be done based on the
> > actual availability of the exported function - using module_info/1
> > for that; Dialyzer would then detect a potential call to a
> > non-existing function, it would be neat if we could specify that
> > these warnings should be suppressed as we know that this cannot
> > happen).


---------------------------
Olivier Boudeville

EDF R&D : 1, avenue du Général de Gaulle, 92140 Clamart, France
Département SINETICS, groupe ASICS (I2A), bureau B-226
Office : +33 1 47 65 59 58 / Mobile : +33 6 16 83 37 22 / Fax : +33 1 47 
65 27 13



Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse.

Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message.

Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus.
____________________________________________________

This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval.

If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message.

E-mail communication cannot be guaranteed to be timely secure, error or virus-free.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150717/6e5af62e/attachment.htm>


More information about the erlang-questions mailing list