1:00:15jmercourisI'm trying to run the example here: https://trac.clozure.com/ccl/wiki/CocoaBridge and instead of drawing a red window, I just get the following: https://imgur.com/a/64OxP
1:07:27jmercourisIt's interesting because it updates the "Window" section of the menubar, but the window is NOT visible, even when using "Bring all to front"
1:48:35jmercourisI'm assuming this is due to changes in Cocoa
1:48:47jmercourisI guess I'll have to rewrite the example, and re-learn a lot of Cocoa
2:14:00jmercouriscan anyone reccomend a good cffi tutorial?
2:16:14jmercourisI'm looking at it now, seems pretty good, but just wondering if there was something else, I like reading from multiple resources usually
4:38:39shrdlu68In the loop above it looks you don't need the into and return keywords. i.e. (loop for x from 1 to (1- (length stringA)) collecting x) would suffice.
10:35:19flip214hmmm, CFFI::FOREIGN-STRING-LENGTH is using 40% of the CPU time... ouch.
10:55:26beachIs there an appropriate existing error condition that could be signaled if an attempt is made to execute a form that had compilation errors.
11:06:14phoe_lexixal is PROGRAM-ERROR, dynamic is CONTROL-ERROR.
11:06:21phoe_"The errors that result from giving throw a tag that is not active or from giving go or return-from a tag that is no longer dynamically available are of type control-error."
11:06:29beachsb-int:compiled-program-error it is for SBCL
11:06:44beach(defun f (x) (let 234 x)) and then (f 234)
11:07:09phoe_ Class precedence-list: SB-INT:COMPILED-PROGRAM-ERROR, PROGRAM-ERROR, ERROR, SERIOUS-CONDITION, CONDITION, SB-PCL::SLOT-OBJECT, T
11:09:36phoe_I think that when it encounters compile-time erroring code, it actually bakes the found condition in the compiled code and then signals it.
11:09:53phoe_I'd need to look at the decompiled code of (lambda () (go 3)) for example.
11:11:45beachIt compiles a call to ERROR that signals a condition of type sb-int:compiled-program-error, and that condition contains the instance of the error signaled at compile time.
11:13:13phoe_beach: yes, thank you. That's the correct order.
11:14:23phoe_minion: memo for Xach: your domain lisptips.com expired.
11:14:23minionRemembered. I'll tell Xach when he/she/it next speaks.
11:26:57beachSo the restartable-form I have may signal a compile-time error and I want to store that error condition in the run-time error condition. I came up with this solution: (let (cc) (restart-case (handler-case (form-that-may-signal-an-error) (error (c) (setf cc c) (error c))) (my-restart () (make-condition 'run-time-error :compile-time-error cc))))
11:39:28beachBut it is more complicated. I need to create a FORM that, when executed, makes a condition that includes a condition that existed at compile time.
11:39:47phoe_sounds like a use case for MAKE-LOAD-FORM
11:41:00Bikeinconveniently, i don't think make-load-form-saving-slots works for conditions
11:41:25phoe_Bike: of course it doesn't, conditions aren't standard-objects or structure-objects
11:41:44beachI think I can do something simpler. If this is the file compiler, I just won't attempt to create a FASL, so the compile-time condition does not have to be there.
11:41:44phoe_it will work for most open/free CL implementations except SBCL
11:42:04beachIf it is not the file compiler, I can just include the condition itself in the source code.
12:35:49ShinmeraSometimes the things that are going on in this channel fill me with such inexplicable, explosive rage and fury that I wonder why I even bother coming here at all.