[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

Re: rdoc bug with 'class M::C' syntax

Dave Thomas

10/4/2003 10:41:00 PM


On Saturday, Oct 4, 2003, at 16:37 US/Central, Joel VanderWerf wrote:

>
> I wonder if anyone else has seen this with the recent CVS of Rdoc. It
> wasn't happening as recently as 28 May 2003, but with the 23 Sep 2003
> CVS, using M::C when M is in a required file causes a problem.
>
> ==== a.rb ====
> require './m'
> # module M; end # this prevents the problem
>

In the past, RDoc didn't bother to look for the actual definition of
modules, but now it does. However, it also does not actually execute
your program, so it doesn't perform the require, and hence doesn't load
up module 'M' before you then use it later in the code.

There are two fixes: in the short term, simply put the file containing
the definition of M earlier in the command line to RDoc. When I get a
chance I'll fix RDoc to dummy up the module M in this case
automatically.

Cheers

Dave
2 Answers

Joel VanderWerf

10/4/2003 11:12:00 PM

0

Dave Thomas wrote:
>
> On Saturday, Oct 4, 2003, at 16:37 US/Central, Joel VanderWerf wrote:
>
>>
>> I wonder if anyone else has seen this with the recent CVS of Rdoc. It
>> wasn't happening as recently as 28 May 2003, but with the 23 Sep 2003
>> CVS, using M::C when M is in a required file causes a problem.
>>
>> ==== a.rb ====
>> require './m'
>> # module M; end # this prevents the problem
>>
>
> In the past, RDoc didn't bother to look for the actual definition of
> modules, but now it does. However, it also does not actually execute
> your program, so it doesn't perform the require, and hence doesn't load
> up module 'M' before you then use it later in the code.

Actually, I had the same problem with either order of the two files. It
didn't help to see the file containing the definition of M first.

I'm happy with the older version, for now. Thanks!

Axel Kühn

1/12/2010 10:27:00 AM

0

Hi,

> - On the AOS server: Go to control pannel - add/remove programs - check
> "show updates" - scroll down to your AOS instance, the KB's should be there
well, this could also work for AX 4.0. But in the past there were some
Hotfixes which are provided whithout an installer (only a xpo file). Theses
HotFixes ar not shown there.

For Ax 4.0 the class SysHotfixManifest is not available.
--
Sincerely yours
Axel K??hn (visit my Dynamics AX blog at: http://blog.a...)


"Klaas Deforche" wrote:

> Hi,
>
> This applies to AX2009, but it could apply to AX40 too (I don't have AX40
> installed now so I can't check):
>
> - On the AOS server: Go to control pannel - add/remove programs - check
> "show updates" - scroll down to your AOS instance, the KB's should be there
>
> - In AX, open the AOT, and go to the class SysHotfixManifest. There is a
> method in this class for each KB hotfix that is installed.
>
> Again, this applies for AX2009, I'm not sure about AX40.
>
> Best regards,
> Klaas.
> ----------------
> http://www.artofc...
>
>
> "Axel K??hn" wrote:
>
> > HI,
> >
> > this is a very interesting question.
> > I don't know any website, document, etc. which provides these informations.
> >
> > On CustomerSource or PartnerSurce you can find descriptions for i.e the
> > HotFix-Rollups describing each HotFix which is part of the HotFix-Rollup.
> > But if you have installed some HotFixes seperatly i think there is no way to
> > identify whcih hotfixes are installed an which ar not.
> >
> > But it could be possible that someone from MS can help you identifing the
> > installed hotfixes based on the Application Version.
> > --
> > Sincerely yours
> > Axel K??hn (visit my Dynamics AX blog at: http://blog.a...)
> >
> >
> > "ggg" wrote:
> >
> > > How do I know which hotfixes have been installed in a Dynamics Ax 4.0
> > > instance?? Is it possible to identify them exactly?
> > >
> > >
> > >
> > > __________ Information from ESET NOD32 Antivirus, version of virus signature database 4755 (20100108) __________
> > >
> > > The message was checked by ESET NOD32 Antivirus.
> > >
> > > http://ww...
> > >
> > >
> > >
> > >
> > > .
> > >