1.1 final. Brian: no specific reason, it's just faster if i don't ;D but if the default access level is ever changed i'd be in trouble. i'm just hoping they wouldn't be that mad...
On Apr 4, 1:40 am, Mark Mandel <[email protected]> wrote: > Which version is this? I thought I had allowed for it, possibly in > 1.1? I will have a look. > > Mark > > > > On Sat, Apr 4, 2009 at 5:21 AM, Brian Kotek <[email protected]> wrote: > > While I suppose Mark could add this pretty easily, it sounds like a pretty > > bad decision to not specify the access level of a method. Is there a reason > > you don't want to clearly specify the access level? > > > On Fri, Apr 3, 2009 at 11:02 AM, Chris H <[email protected]> wrote: > > >> If the access property of a function is not defined, it defaults to > >> public. But Transfer is looking for it during during the creation of > >> the "advise" method creation, because an "Element ACCESS is undefined > >> in METADATA.:" error is thrown if it is not explicitly defined. can > >> this be fixed to use the default of "public" when it is undefined? > > -- > E: [email protected] > W:www.compoundtheory.com --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
