- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Having comments for pragma?

by Eliot Miranda

Hi Doru, > On Jun 30, 2016, at 1:08 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > >> On Jun 27, 2016, at 7:55 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi Doru, >> >> On Mon, Jun 27, 2016 at 6:36 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Hi Eliot, >> >> I agree with most things you say (except the conclusion :)), and I think that we are talking about complementary issues. >> >> As I mentioned before, there already is a need to distinguish between a plain selector and one that is associated with pragmas. This is what you find in PragmaType in Spotter and Inspector. This is a kind of meta-object and having it adds value. I can search for pragmas âtypeâ (we can also call it a PragmaSelector), and I can distinguish between all occurrences of a pragma âtypeâ and its utilization in computation. But, the current implementation of PragmaType is a mere pseudo-meta-object, given that it has no casual connection to the runtime. >> >> What we know from Smalltalk is that the analysis model does not have to differ from the runtime one. The consequence is that every time we do see a difference, we should investigate because we might uncover a hidden need opportunity. >> >> I know the VW model, and indeed, we could have something like: >> >> MyConcept class>>myPragmaDefinition >> âa comment about the pragma" >> <pragma: #selector> >> >> However, this only deals with the definition of the pragma type not with the internal representation. There could still well be an object that encapsulates both the selector and the comment. And that object would also allow us to build tools around it. We could call it a PragmaType, PragmaDefinition, or even PragmaSelector. And we could get the Pragma to point to this type either through an inst var or through a query (I would probably prefer an instvar). >> >> Well, there already /is/ a meta-object called Pragma, and it gets instantiated when one accesses the compiled method via pragmas: >> >> (CompiledMethod allInstances detect: [:m| m pragmas size > 1]) pragmas collect: [:ea| {ea. ea class}] {{<export: true> . Pragma} . {<var: #tablePtr type: 'int *'> . Pragma}} > > Yes I know :). An instance of Pragma denotes an concrete annotation of a method. I now would like a meta-object that describes all Pragma instances having the same selector. For example, the protocol on the class side of the Pragma class is actually a query protocol that is better suited for the instance side of a PragmaDescription meta-object. For example: > > Pragma class>>allNamed: aSymbol in: aClass > > would become > > PragmaDescription>>pragmasIn: aClass > > and you would use it like: > > (PragmaDescription named: aSymbol) pragmasIn: aClass > > Creating an instance of PragmaDescription would imply searching the image for the <pragma:> definition. I like this. > I would also like to have a Flyweight pool per environment such that we always get only one instance of a PragmaDefinition per selector (like it happens with Symbols). Yes, good refinement. >> So we could add the information you want to Pragma, and have it be lazy. > > It does not quite belong to the Pragma. A comment is common to all Pragma instances, and having it duplicated at the instance level is less elegant. > > But, looking for the users (all senders of the pragma selector - the methods that use the annotation) of a Pragma would be even less inconvenient to have on the instance side of Pragma. > > >> The Pragma could go search for the defining class-side pragma methods and use the parser to extract the comment(s) when asked. Hence simple access to pragmas, interested only in the selectors for applying, wouldn't have their performance be impacted. > > The design sketched above would require no runtime penalty for a Pragma instance. All code that works now would work identically afterwards. We would only have one selector in Pragma to get the corresponding description: > > Pragma>>description > ^ PragmaDescription named: self selector > > Alternatively, we could modify the compilation to associate the PragmaDescription in an inst var of a Pragma instance. So, CompiledMethod>>pragmas would always return instances of Pragmas with a PragmaDefinition inst var. > > I think I would start with the lazy lookup first, and this would disturb nothing from the current behavior. Sounds like a reasonable plan. > > >> I think that this proposition does not remove from the simplicity of the implementation at all, but allows the new needs to be accommodated nicely. The alternative is to not do anything, in which case we will continue to have an analysis-only-pseudo-meta-object which is not nice at all. I do not think we should jump on this lightly, but I do think we should have a critical look and evaluate the options. >> >> This pseudo-meta-object (Pragma) can sty ill be causally connected, in the same way that a MethodReference can be causally connected. The causation is things like "remove", "recompile", but that's dubious. It's essentially a read-only relationship; one wants to be able to locate the method from the pragma, but changing the method from the pragma isn't necessarily a good idea. Would you agree that convenience methods like "remove" on MethodReference are a bad idea and one should stick to the removeSelector: protocol on Behavior and ClassDescription? >> >> >> What do you think? >> >> Have I and enough coffee to scramble my thoughts might be a more pertinent question ;-) > > :) > > Cheers, > Doru > > >> >> Cheers, >> Doru >> >> >>> On Jun 27, 2016, at 2:39 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>> >>> Hi Doru, >>> >>>> On Jun 27, 2016, at 3:52 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> Hi, >>>> >>>> The CompiledMethod already has a way to retrieve Pragma instances: >>>> >>>> CompiledMethod>>pragmas. >>>> >>>> However, the Pragma instance does not have a meta-object associated with it. So, I would first start from adding that one and linking such a PragmaType to its instances. The important thing here would be that all Pragma instances with a certain selector should reference the same PragmaType. >>> >>> Let me express a dissenting opinion. Our pragma system is minimal yet powerful. By using Message instances (with literal arguments) to represent pragmas we get >>> - executable pragmas that can be applied using perform: or wrappers such as sentTo: >>> - we can use conventional browsing queries (implementors and senders) to discover which methods are marked by a specific pragma and what pragma-processing tools implement a specific pragma. >>> - a rich pragma language that can have many, named parameters >>> - a system which doesn't need its own language, but reuses the existing Smalltalk parsing facilities, and so is easier to learn and to implement >>> >>> So its parsimony is an important part of its virtues. It is minimal. >>> >>> One thing missing from the Squeak/Pharo implementation is the set of legal pragmas a class accepts. In VisualWorks a class implements the <pragma: #pragma:selector:> (it might be <pragmas: #(pragma:selector:one: pragma:selector:two:)>) to define the legal set of pragmas. [Implementation note, these are /not/ searched for ahead of compilation; instead, the parser delays searching for class-side methods containing pragma: pragmas until it encounters a pragma, and it searches for all class side methods, including in superclasses). >>> >>> This scheme allows pragmas to be checked; only pragmas in the set of allowed pragmas are accepted, and it allows collision-free extensibility; any package can add a set of legal pragmas to a class merely by choosing a method selector that won't collide with any other containing pragma: pragmas, eg >>> kernelPragmas >>> <pragma: #primitive:> >>> <pragma: #primitive:error:> >>> <pragma: #primitive:module:> >>> <pragma: #primitive:module:error:> >>> >>> We're missing this, which means our compilers don't safely check for valid pragmas and can't reject invalid or unrecognized ones, which is error prone. >>> >>> If we implemented this then we would have a natural place to comment pragmas in the method that defines a particular pragma, one that would be found using senders. >>> >>> None of this requires a meta object. It is perfectly recursive; using itself to implement itself. I find this very elegant (I didn't invent pragma: pragmas; Steve Dahl did, and it's a cool idea). >>> >>> So as an inventor of pragmas I'd like to ask for the minimal implementation outlined above. I'd like that we didn't j tricycle a specific meta object, with all the additional tools that implies, and instead stick to the minimalist and parsimony of the original design and use pragmas to comment pragmas. >>> >>>> Cheers, >>>> Doru >>> >>> Thanks for reading. >>> Cheers, Eliot >>> >>>>> On Jun 27, 2016, at 12:34 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>>>> >>>>> >>>>> 2016-06-27 12:12 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: >>>>> Hi, >>>>> >>>>> That is my proposal as well: introduce a first class entity that describes a Pragma instance. Who would be interested to play with this? >>>>> >>>>> How it could be done? >>>>> Probably compiler could search preferred Pragma class for given selector. And then we will have collection of real pragma instances inside CompiledMethod. What do you think? >>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "Be rather willing to give than demanding to get." >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "When people care, great things can happen." >> >> >> >> >> >> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot > > -- > www.tudorgirba.com > www.feenk.com > > "Not knowing how to do something is not an argument for how it cannot be done." > >

July 7, 2016

Re: [Pharo-dev] [squeak-dev] Time now print24

by Chris Muller

Hi Eliot, wanted the exact same thing, a short terse representation so I made one that employs "present context" -- e.g., if it is same day as today, just print the time, otherwise include both the Date and Time. This should be extended so if it is outside the current year, then it should include the year, otherwise not. Here's the old method, which could use a update, since #makeUTC is no longer necessary either.. printAbbreviatedOn: aStream | date | (date := self asDate) makeUTC = Date today ifTrue: [ self asTime print24: false showSeconds: false on: aStream ] ifFalse: [ aStream maPrint: ((date printFormat: #(2 1 3 $/ 1 2 1 )) copyUpToLast: $/) ; maPrint: $@. self asTime print24: false showSeconds: false on: aStream ] Another approach -- you could also play around with DateAndTime>>#printYMDOn:. On Thu, Jul 7, 2016 at 11:33 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi All, > > how does one produce a nice timestamp, simply date and time as in > > 7/7/2016 09:19:38 > > Trivial, right? > > So > > Date today mmddyyyy, ' ', Time now print24 '7/7/2016 09:22:40.914' > > .914, ah, nanos. How useful. Let's get rid of them. No nanos: accessor so > > Date today mmddyyyy, ' ', (Time now nanos: 0) print24 => MNU > > but there's a seconds accessor, so > > Date today mmddyyyy, ' ', (Time now seconds: Time now seconds; print24) > '7/7/2016 00:00:41 > > ?? So seconds: is private, and isn't the dual of Time seconds: > > Time seconds > ^ self second > Time second > ^ self asDuration seconds > Duration seconds > "Answer the number of seconds the receiver represents." > ^seconds rem: SecondsInMinute > > Looks broken to me. > > Personally I think print24 should not print sub seconds. > > cc'ing to Pharo because I want this timestamp to be the same in both > dialects for a profiling tool we want to use in both dialects. > _,,,^..^,,,_ > best, Eliot > > >

July 7, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60141 Home: https://github.com/pharo-project/pharo-core

July 7, 2016

[pharo-project/pharo-core] fb9425: 60141

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: fb9425d70ed5405074e24c43b830fb331cd6c3a0 https://github.com/pharo-project/pharo-core/commit/fb9425d70ed5405074e24c43… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-07 (Thu, 07 Jul 2016) Changed paths: M Collections-Strings.package/Symbol.class/README.md M Kernel.package/Deprecation.class/instance/handling/transform.st M Kernel.package/Object.class/class/documentation/whatIsAPrimitive.st M OpalCompiler-Tests.package/IRBuilderTest.class/instance/testing - blocks/testRemoteTemp.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/examples/remoteTemp.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/examples/remoteTempNested.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60140.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60141.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60140.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60141.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60141 17958 Add examples to the Symbol class comment https://pharo.fogbugz.com/f/cases/17958 18618 Better additional comment for primitive: 79 error: ec usage https://pharo.fogbugz.com/f/cases/18618 18697 Automatic deprecation refactoring needs to take traits into account https://pharo.fogbugz.com/f/cases/18697 18700 SistaV1 bytecode: fix for Opal tests to not crash the image https://pharo.fogbugz.com/f/cases/18700 http://files.pharo.org/image/60/60141.zip

July 7, 2016

Re: [Pharo-dev] Time now print24

by Sven Van Caekenberghe

> On 07 Jul 2016, at 18:33, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi All, > > how does one produce a nice timestamp, simply date and time as in > > 7/7/2016 09:19:38 > > Trivial, right? I understand that you want it 'nice and clean', but the above is not precise (no TZ) and confusing (is it M/D/YYYY or D/M/YYYY ?). Going more in the ISO direction is better (more universal), IMHO. DateAndTime now rounded => "2016-07-07T18:45:12+02:00" > So > > Date today mmddyyyy, ' ', Time now print24 '7/7/2016 09:22:40.914' > > .914, ah, nanos. How useful. Let's get rid of them. No nanos: accessor so > > Date today mmddyyyy, ' ', (Time now nanos: 0) print24 => MNU > > but there's a seconds accessor, so > > Date today mmddyyyy, ' ', (Time now seconds: Time now seconds; print24) '7/7/2016 00:00:41 > > ?? So seconds: is private, and isn't the dual of Time seconds: > > Time seconds > ^ self second > Time second > ^ self asDuration seconds > Duration seconds > "Answer the number of seconds the receiver represents." > ^seconds rem: SecondsInMinute > > Looks broken to me. > > Personally I think print24 should not print sub seconds. > > cc'ing to Pharo because I want this timestamp to be the same in both dialects for a profiling tool we want to use in both dialects. > _,,,^..^,,,_ > best, Eliot

July 7, 2016

Time now print24

by Eliot Miranda

Hi All, how does one produce a nice timestamp, simply date and time as in 7/7/2016 09:19:38 Trivial, right? So Date today mmddyyyy, ' ', Time now print24 '7/7/2016 09:22:40.914' .914, ah, nanos. How useful. Let's get rid of them. No nanos: accessor so Date today mmddyyyy, ' ', (Time now nanos: 0) print24 => MNU but there's a seconds accessor, so Date today mmddyyyy, ' ', (Time now seconds: Time now seconds; print24) '7/7/2016 00:00:41 ?? So seconds: is private, and isn't the dual of Time seconds: Time seconds ^ self second Time second ^ self asDuration seconds Duration seconds "Answer the number of seconds the receiver represents." ^seconds rem: SecondsInMinute Looks broken to me. Personally I think print24 should not print sub seconds. cc'ing to Pharo because I want this timestamp to be the same in both dialects for a profiling tool we want to use in both dialects. _,,,^..^,,,_ best, Eliot

July 7, 2016

Re: [Pharo-dev] confused about the "image opening session"

by Denis Kudriashov

Hi 2016-07-06 9:00 GMT+02:00 Christophe Demarey <christophe.demarey(a)inria.fr>: > yes, what is bad now is that there is âno crash detectorâ. > If you quit an image without saving, you will get the epicea browser. I do > not want it in this case. When I do not save, it is on purpose. > Maybe a flag should be set when you quit the image (by saving or not). > This way, if the flag is not present at image startup, you could guess a > crash. > We could introduce special Epicea event "Image Shutdown". In this case current detector will not detect lost changes. Right now it analyses that last event is about code change. I guess it is not difficult to do and there is existing example: "image snapshot" event.

July 7, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

by Esteban Lorenzano

I have to add hereâ¦ solution is bad, because now projects are not shown EVEN if I activate it in settings :( > On 06 Jul 2016, at 12:28, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > yes, I do not agree either but is true there where problems. > but IMO this would be solved just by putting a timeout in 1-2s (and then run in background, and cache results) > not turning it off. > in for my experience, turning something off is equivalent to remove the feature (but then is worst, because it becomes dead code inside image). > > Anyway, any taker, to solve this in a proper way? > > Esteban > >> On 06 Jul 2016, at 12:13, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>> On 06 Jul 2016, at 10:12, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> >>>> On 06 Jul 2016, at 09:52, GitHub <noreply(a)github.com> wrote: >>>> >>>> 18674 Turn spotter catalog off by default >>>> https://pharo.fogbugz.com/f/cases/18674 >>> >>> We did not agree on this, at all, there was no public discussion, no vote. >>> >> >> I only know that there where problems. >> >> Marcus >> >

July 7, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60140 Home: https://github.com/pharo-project/pharo-core

July 7, 2016

[pharo-project/pharo-core] b6f7fb: 60140

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: b6f7fb4f49a031aac861ae87409687c3ac80f744 https://github.com/pharo-project/pharo-core/commit/b6f7fb4f49a031aac861ae87… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-07 (Thu, 07 Jul 2016) Changed paths: M FileSystem-Smalltalk.package/extension/CompiledMethod/instance/fileSize.st M GT-InspectorExtensions-Core.package/extension/CompiledMethod/instance/gtInspectorSourceIn_.st M GT-SpotterExtensions-Core.package/extension/CompiledMethod/instance/spotterPreviewCodeIn_.st M Glamour-Examples.package/GLMBasicExamples.class/instance/others/watcher.st M Glamour-Morphic-Brick.package/GLMCompositeBrick.class/class/examples/gtExamplePharoMethod.st M Kernel.package/CompiledMethod.class/instance/source code management/getSource.st M Network-Mail.package/MailAddressTokenizer.class/class/initialization/initialize.st M Network-Tests.package/MailAddressParserTest.class/instance/tests/testAddressesIn.st A Network-Tests.package/MailAddressParserTest.class/instance/tests/testAmpersand.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/examples/pushClosureCopyNoCopied.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/examples/pushClosureCopyNoCopiedArg.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/examples/pushClosureCopyOneCopiedArg.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/examples/remoteTemp.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/examples/remoteTempNested.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - blocks/testPushClosureCopyNoCopied.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - blocks/testPushClosureCopyNoCopiedArg.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - blocks/testPushClosureCopyOneCopiedArg.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - blocks/testPushClosureCopyOneCopiedTemp.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - examples/testDecompileBytecodeDecompilerTestClass.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - examples/testDecompileBytecodeGeneratorTest.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - examples/testDecompileIRBuilderTestClass.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testBugOffset.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testDup.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testInstVar.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testJumpAheadTo.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testJumpAheadToIf.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testJumpBackTo.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralArray.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralBoolean.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralCharacter.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralFloat.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralInteger.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralNil.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralString.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralSymbol.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralVariableClass.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralVariableClassVariable.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralVariableGlobale.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPopTop.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPushConsArray.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPushConsArray2.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPushSelf.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPushTempArgument.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPushTempTemp.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPushThisContext.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testRemoteTemp.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testRemoteTempNested.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testReturnTop.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testSendSuper.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testStoreIntoVariable.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testStoreTemp.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60139.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60140.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60139.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60140.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60140 18696 some cleanup for OCBytecodeDecompilerTest for new Bytecode set https://pharo.fogbugz.com/f/cases/18696 18680 Forward port 18676 Endless loop parsing e-mail addresses containing an ampersand https://pharo.fogbugz.com/f/cases/18680 18694 deprecate #getSource https://pharo.fogbugz.com/f/cases/18694 http://files.pharo.org/image/60/60140.zip

July 7, 2016